Triple
T685847
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beijing Daxing International Airport |
E13280
|
entity |
| Predicate | terminalType |
P9111
|
FINISHED |
| Object | single-terminal |
—
|
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: single-terminal | Statement: [Beijing Daxing International Airport, terminalType, single-terminal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terminalType Context triple: [Beijing Daxing International Airport, terminalType, single-terminal]
-
A.
terminal
Indicates that one entity is the final or end point in a process, sequence, or structure, beyond which no further continuation occurs.
-
B.
terminusType
chosen
Indicates the specific kind or role of an endpoint or terminal within a route, network, or process.
-
C.
systemType
Indicates the classification or category of a system that an entity belongs to or operates as.
-
D.
definesDeviceType
Indicates that one entity specifies or assigns the device type classification of another entity.
-
E.
shellType
Indicates the type or classification of a shell associated with an entity (e.g., its form, structure, or category).
- 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_69a4933e0f98819097d22766c49b61b8 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4a0f55f7481909e052a25bd12d455 |
completed | March 1, 2026, 8:26 p.m. |
| PD | Predicate disambiguation | batch_69a49d2048d48190ab99ab59accb6909 |
completed | March 1, 2026, 8:10 p.m. |
Created at: March 1, 2026, 7:36 p.m.