Triple
T25265021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ZBTJ |
E633406
|
entity |
| Predicate | partOfAirspaceRegion |
P161488
|
FINISHED |
| Object | North China air traffic control region |
—
|
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: North China air traffic control region | Statement: [ZBTJ, partOfAirspaceRegion, North China air traffic control region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfAirspaceRegion Context triple: [ZBTJ, partOfAirspaceRegion, North China air traffic control region]
-
A.
appliesToAirspaceOf
Indicates that a rule, restriction, or condition is specifically relevant to, or in effect within, a particular airspace.
-
B.
airspaceType
Indicates the classification or category of airspace that applies to a given location or flight segment.
-
C.
isInAirspaceRegion
chosen
Indicates that an entity is located within or passing through a specified airspace region.
-
D.
fareControlAreaLocatedIn
Indicates that a fare control area (e.g., turnstiles or ticket gates) is physically located within a specified larger facility or space.
-
E.
partOfLandingSector
Indicates that one entity constitutes a component or subdivision within a larger landing sector.
- 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_69e75a922ad481908f4f1f884583cb42 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f68805b4848190b75da14996d52a38 |
completed | May 2, 2026, 11:25 p.m. |
| PD | Predicate disambiguation | batch_69f68609c0b08190a8e1238a4d97c270 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 21, 2026, 1:14 p.m.