Triple
T26025213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LJ |
E647269
|
entity |
| Predicate | airlineMainHubLocation |
P4364
|
FINISHED |
| Object | Incheon |
—
|
NE NERFINISHED |
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: Incheon | Statement: [LJ, airlineMainHubLocation, Incheon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: airlineMainHubLocation Context triple: [LJ, airlineMainHubLocation, Incheon]
-
A.
associatedAirportPrimaryHubFor
Indicates that an airport serves as the primary hub for a particular airline or transportation operator.
-
B.
airlineBaseCity
Indicates the city that serves as the primary operational base or headquarters location for an airline.
-
C.
airlineHub
chosen
Indicates that a particular location (typically an airport or city) serves as a central hub or primary operational base for an airline.
-
D.
linkedAirlineHeadquartersLocation
Indicates that an airline’s headquarters is located in the specified place or facility.
-
E.
originAirportHub
Indicates that the referenced airport serves as a primary hub or main operating base for the associated airline or carrier.
- 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_69e77e8b60e88190a3b26c4f0032a2c2 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f605ea27648190b481ce5a9c0aef22 |
completed | May 2, 2026, 2:10 p.m. |
| PD | Predicate disambiguation | batch_69f5f7fba5248190945acf1561280799 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 22, 2026, 9:05 a.m.