Triple
T34439781
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SQ22 |
E884064
|
entity |
| Predicate | airportPair |
P134491
|
FINISHED |
| Object | SIN–JFK |
—
|
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: SIN–JFK | Statement: [SQ22, airportPair, SIN–JFK]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: airportPair Context triple: [SQ22, airportPair, SIN–JFK]
-
A.
airportCodePair
chosen
Indicates a relationship between two entities where each is associated with a specific airport code, typically representing a pair of airports linked in some context such as a route or connection.
-
B.
airportCodeContext
Indicates that an airport code is being used or interpreted within a specific contextual framework (such as a region, system, or standard) that defines its meaning.
-
C.
airportIdentifier
Indicates that an entity is identified by a specific airport code or designation within an aviation identification system.
-
D.
airportUse
Indicates that an airport is used or utilized by a particular entity, such as an airline, organization, or service.
-
E.
airportCodeFAA
Indicates that an airport is identified by a specific FAA (Federal Aviation Administration) airport code.
- 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_69f349c548d88190978e2a82502c03d0 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f727bde8f88190ad746ca515134ca1 |
completed | May 3, 2026, 10:47 a.m. |
| PD | Predicate disambiguation | batch_69f72739c30c81908642eef3feb3afcf |
completed | May 3, 2026, 10:45 a.m. |
Created at: May 1, 2026, 2 a.m.