Triple
T2502752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tianhe |
E52502
|
entity |
| Predicate | hasMajorInfrastructureType |
P2560
|
FINISHED |
| Object | international airport |
—
|
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: international airport | Statement: [Tianhe, hasMajorInfrastructureType, international airport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMajorInfrastructureType Context triple: [Tianhe, hasMajorInfrastructureType, international airport]
-
A.
hasInfrastructureType
chosen
Indicates that an entity possesses or is associated with a specific category or type of infrastructure.
-
B.
isPartOfInfrastructure
Indicates that something belongs to, is included within, or functions as a component of a larger infrastructure system.
-
C.
hasMajorBridge
Indicates that one entity possesses or includes a primary or significant bridge associated with it.
-
D.
hasMajorRailCorridor
Indicates that a location or region is traversed by a primary, high-capacity railway route used for significant passenger or freight transport.
-
E.
hasMajorTransportationRole
Indicates that an entity plays a primary or significant role in providing or supporting transportation services or infrastructure.
- 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_69ab4957b3a88190adf968ae0c1b931c |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abd1cb4f6481908d4e0a1dc0d84d3c |
completed | March 7, 2026, 7:20 a.m. |
| PD | Predicate disambiguation | batch_69abd0bba5348190bb4637d3165cb339 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:46 p.m.