Triple
T30155565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 长江武汉段 |
E766509
|
entity |
| Predicate | 通航等级 |
P168506
|
FINISHED |
| Object | 高等级航道 |
—
|
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: 高等级航道 | Statement: [长江武汉段, 通航等级, 高等级航道]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 通航等级 Context triple: [长江武汉段, 通航等级, 高等级航道]
-
A.
airworthinessCategory
Indicates the regulatory airworthiness classification assigned to an aircraft or component, defining the standards and conditions under which it is approved to operate.
-
B.
ICAOClassificationSystem
Indicates a relationship where an entity is categorized or defined according to the standards and categories of the ICAO (International Civil Aviation Organization) classification system.
-
C.
operationalAltitudeBand
Indicates the range of altitudes within which an entity is intended or allowed to operate.
-
D.
FAAclassification
Indicates the type or category assigned to something under the Federal Aviation Administration’s (FAA) classification system.
-
E.
hasAirportClassification
Indicates that an airport is assigned a specific classification or category based on defined criteria.
- F. None of above. chosen
Provenance (4 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_69f22479cd088190ab4c6f3fce39d1c5 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67ed72fb08190955d6bfd90dd3b8e |
completed | May 2, 2026, 10:46 p.m. |
| PD | Predicate disambiguation | batch_69f673c7a4588190837854f3ef61e6bf |
completed | May 2, 2026, 9:59 p.m. |
| PDg | Predicate description generation | batch_69f6749f205c81909d1aacf462912eee |
completed | May 2, 2026, 10:03 p.m. |
Created at: April 29, 2026, 7:20 p.m.