Triple
T13076770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LPQ |
E329595
|
entity |
| Predicate | UNLOCODEStatus |
P1800
|
FINISHED |
| Object | not a UN/LOCODE (IATA only) |
—
|
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: not a UN/LOCODE (IATA only) | Statement: [LPQ, UNLOCODEStatus, not a UN/LOCODE (IATA only)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: UNLOCODEStatus Context triple: [LPQ, UNLOCODEStatus, not a UN/LOCODE (IATA only)]
-
A.
UNLOCODE
chosen
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.
ISO3166Status
Indicates the classification or current standing of an entity under the ISO 3166 country code standard (e.g., official, reserved, or deleted status).
-
D.
countrySpecificStatus
Indicates a status or condition that is defined or applied specifically in the context of a particular country.
-
E.
statusInUnitedStates
Indicates the legal or official standing that an entity holds within the jurisdiction of the United States.
- 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_69d80771749c81909a6d9197b9504872 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d9811828448190ac6ddd3e9c221251 |
completed | April 10, 2026, 11 p.m. |
| PD | Predicate disambiguation | batch_69d9803d46688190bac6b7d208f08d01 |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9:01 p.m.