Triple
T32575349
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | THBKK |
E832627
|
entity |
| Predicate | isCodedIn |
P1444
|
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: [THBKK, isCodedIn, UN/LOCODE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCodedIn Context triple: [THBKK, isCodedIn, UN/LOCODE]
-
A.
codifiedIn
Indicates that something is formally recorded, defined, or established within a specific document, code, or legal/institutional text.
-
B.
codifiedFor
Indicates that something has been formally organized, standardized, or written down specifically for use by or application to another entity.
-
C.
encodedIn
chosen
Indicates that one entity is represented, stored, or expressed within another entity using a specific encoding or format.
-
D.
isCodifiedFormOf
Indicates that one entity is the formal, standardized, or officially documented version or expression of another entity.
-
E.
codifiedThrough
Indicates that something is formally established, expressed, or made authoritative by means of a specific codification process, document, or legal/institutional mechanism.
- 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_69f349289adc81909f4374a58ec35a39 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c63e3ac081908cd2ee069e971cea |
completed | May 3, 2026, 3:51 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2c138481908afa3ee3e91f8900 |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 1:04 a.m.