Triple
T868749
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UN M49 |
E18763
|
entity |
| Predicate | codingScheme |
P18653
|
FINISHED |
| Object | three-digit numeric codes |
—
|
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: three-digit numeric codes | Statement: [UN M49, codingScheme, three-digit numeric codes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: codingScheme Context triple: [UN M49, codingScheme, three-digit numeric codes]
-
A.
hasCodeScheme
chosen
Indicates that something is associated with or organized according to a particular coding or classification scheme.
-
B.
codifiedIn
Indicates that something is formally recorded, defined, or established within a specific document, code, or legal/institutional text.
-
C.
codificationLevel
Indicates the degree or extent to which something is formally systematized, standardized, or encoded into an explicit set of rules or structures.
-
D.
codeStandard
Indicates that an entity adheres to, complies with, or is governed by a specified coding or programming standard.
-
E.
codeType
Indicates the classification or category assigned to a particular code within a coding or encoding system.
- 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_69a4938ce8688190a24bdfef82ba7d21 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4ac7f98908190883f71049092c7c8 |
completed | March 1, 2026, 9:15 p.m. |
| PD | Predicate disambiguation | batch_69a4aa87504481909618a6815948da6f |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:39 p.m.