Triple
T2158852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CY |
E47954
|
entity |
| Predicate | relatedNumericCodeType |
P508
|
FINISHED |
| Object | ISO 3166-1 numeric code |
—
|
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: ISO 3166-1 numeric code | Statement: [CY, relatedNumericCodeType, ISO 3166-1 numeric code]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedNumericCodeType Context triple: [CY, relatedNumericCodeType, ISO 3166-1 numeric code]
-
A.
numericCode
chosen
Indicates that an entity is associated with a specific numerical identifier or classification code.
-
B.
relatedCodeSet
Indicates that one code set is associated with or connected to another code set in a meaningful or defined way.
-
C.
relatedCode
Indicates that one code is associated with, linked to, or otherwise contextually connected to another code.
-
D.
relatedConstant
Indicates that one entity is a fixed, unchanging value or constant that is associated with or linked to another entity.
-
E.
regionCodeType
Indicates the classification or format type used for a given region code within a coding or identification 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_69a88a1d1fd8819088b34990d69a712f |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abbe6a412c8190ae632282650739d9 |
completed | March 7, 2026, 5:58 a.m. |
| PD | Predicate disambiguation | batch_69abbd9c90408190b6b65498ca43ce26 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:45 p.m.