Triple
T8188761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terminal 4 (Mehrabad International Airport) |
E191251
|
entity |
| Predicate | arrivalUse |
P33480
|
FINISHED |
| Object | domestic arrivals |
—
|
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: domestic arrivals | Statement: [Terminal 4 (Mehrabad International Airport), arrivalUse, domestic arrivals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: arrivalUse Context triple: [Terminal 4 (Mehrabad International Airport), arrivalUse, domestic arrivals]
-
A.
arrivalAt
Indicates the event or state of an entity reaching and being present at a specific destination or location.
-
B.
arrivalTimePattern
Indicates a recurring or structured pattern in the times at which an entity arrives.
-
C.
departureTime
Indicates the specific time at which an entity leaves or begins its departure from a location or state.
-
D.
arrivalDatePlanned
Indicates the date on which an arrival is scheduled or expected to occur according to a plan.
-
E.
arrivalLocationType
chosen
Indicates the type or category of place where an arrival occurs in the described relationship or event.
- 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_69ca82c5b6948190a583c096fb0a6c71 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb4d9f4a488190b39bdc1792646914 |
completed | March 31, 2026, 4:29 a.m. |
| PD | Predicate disambiguation | batch_69cb36a7952481908f34e3e82f375a84 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:41 p.m.