Triple
T31952727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S.-bound airliners |
E815823
|
entity |
| Predicate | mayArriveAt |
P49364
|
FINISHED |
| Object | major U.S. international airports |
—
|
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: major U.S. international airports | Statement: [U.S.-bound airliners, mayArriveAt, major U.S. international airports]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayArriveAt Context triple: [U.S.-bound airliners, mayArriveAt, major U.S. international airports]
-
A.
arrivalAt
chosen
Indicates the event or state of an entity reaching and being present at a specific destination or location.
-
B.
mayMeetAt
Indicates that two or more entities are permitted or able to have a meeting or encounter at a specified place or time.
-
C.
arrivalFrom
Indicates that an entity arrives at a location or state originating from a specified source location or state.
-
D.
mayMeet
Indicates that one entity is permitted or has the possibility to meet or come together with another entity.
-
E.
arrivalByShip
Indicates that an entity reaches a destination specifically by traveling on a ship.
- 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_69f348f4ec708190abbb2a7c3ed58844 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b2ac9bd481909a1e8adb4e294262 |
completed | May 3, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f6b151ad008190836c1bcdec503ce2 |
completed | May 3, 2026, 2:22 a.m. |
Created at: May 1, 2026, 12:07 a.m.