Triple
T3222271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AO |
E67536
|
entity |
| Predicate | hasAssociatedUNCode |
P1492
|
FINISHED |
| Object | 024 |
—
|
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: 024 | Statement: [AO, hasAssociatedUNCode, 024]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAssociatedUNCode Context triple: [AO, hasAssociatedUNCode, 024]
-
A.
hasUNII
Indicates that one entity is associated with a specific Unique Ingredient Identifier (UNII) code assigned by regulatory authorities.
-
B.
hasUNOrgan
Indicates that an entity is a member of, affiliated with, or otherwise formally associated with a specified United Nations body or organ.
-
C.
hasUNLocode
chosen
Indicates that an entity is associated with a specific UN/LOCODE, identifying its location in the United Nations location code system.
-
D.
associatedWithUnit
Indicates that one entity has a connection, linkage, or affiliation with a particular unit (such as a division, department, or organizational subunit).
-
E.
hasISOCode
Indicates that an entity is associated with a specific standardized ISO code that uniquely identifies it according to ISO conventions.
- 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_69ad858b8adc8190ad989712c87a476b |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adae1845408190b3eccd791231c69c |
completed | March 8, 2026, 5:12 p.m. |
| PD | Predicate disambiguation | batch_69ad9e0bb6c48190a0659c67d40ee37c |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:08 p.m.