Triple
T36750255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CLARI |
E907888
|
entity |
| Predicate | UN/LOCODEScheme |
P1800
|
FINISHED |
| Object | UN/LOCODE |
—
|
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: UN/LOCODE | Statement: [CLARI, UN/LOCODEScheme, UN/LOCODE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: UN/LOCODEScheme Context triple: [CLARI, UN/LOCODEScheme, UN/LOCODE]
-
A.
hasUNLocode
Indicates that an entity is associated with a specific UN/LOCODE, identifying its location in the United Nations location code system.
-
B.
UNLocodeStatus
Indicates the current official status or validity of a UN/LOCODE entry within the UN location code system.
-
C.
portCodeLOCODE
Indicates that a port is identified by a specific LOCODE (Location Code) value.
-
D.
servesAsCargoHubFor
Indicates that one entity functions as a central location or facility for handling, consolidating, and distributing cargo associated with another entity.
-
E.
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.
- 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_69f76e76d10881909ec1679bc043108c |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7c9f5a8848190ba956ff27f44e396 |
completed | May 3, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69f7c8999a348190abc1895eaa6e036d |
completed | May 3, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:12 p.m.