Triple
T33395999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NQZ |
E855171
|
entity |
| Predicate | UNLOCODEType |
P176854
|
FINISHED |
| Object | 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: airport | Statement: [NQZ, UNLOCODEType, airport]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: UNLOCODEType Context triple: [NQZ, UNLOCODEType, airport]
-
A.
UNLOCODE
Indicates that an entity is associated with a specific UN/LOCODE, i.e., a standardized United Nations location code identifying a particular place used in international trade and transport.
-
B.
UNLOCODECountryCode
Indicates that an entity is associated with a specific country code as defined by the UN/LOCODE standard.
-
C.
codeUnitType
Indicates the specific kind or category of a code unit (such as a file, class, method, or module) that a given element belongs to.
-
D.
ISOCode
Indicates that an entity is associated with a specific standardized code defined by the International Organization for Standardization (ISO).
-
E.
regionCodeType
Indicates the classification or format type used for a given region code within a coding or identification system.
- 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_69f3496e3f1c8190bcecfa82aa9d17ff |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f38159d08190980ad639e08f00f4 |
completed | May 3, 2026, 7:04 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d7bee48190b94e0beb48a1d7fa |
completed | May 3, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69f6f37f36ac8190b1bff8711d6771cb |
completed | May 3, 2026, 7:04 a.m. |
Created at: May 1, 2026, 1:35 a.m.