Triple
T25442463
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Four Gates and Forty Stations |
E637542
|
entity |
| Predicate | gateOrder |
P158521
|
FINISHED |
| Object | Tariqa second |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Tariqa second | Statement: [Four Gates and Forty Stations, gateOrder, Tariqa second]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gateOrder Context triple: [Four Gates and Forty Stations, gateOrder, Tariqa second]
-
A.
gateOrder
chosen
Indicates an ordering relationship between gates, specifying the sequence in which one gate precedes or follows another in a process or structure.
-
B.
order
Indicates that one entity requests, arranges, or directs that another entity provide a good, service, or action, typically in a specified sequence or priority.
-
C.
orderAuthority
Indicates that one entity has the formal power or right to issue orders or directives to another entity.
-
D.
orderGroup
Indicates that multiple individual orders are associated together as a single grouped order entity or batch.
-
E.
orderHouse
Indicates that an entity requests or arranges the purchase or construction of a house.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69e75db6c97081908178383fa632b193 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f700162481908c69247082e8a527 |
completed | May 2, 2026, 1:07 p.m. |
| PD | Predicate disambiguation | batch_69f4806d93dc8190b9dff4c63186faff |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 2 p.m.