Triple
T34913865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yotvingian language |
E1006947
|
entity |
| Predicate | hasNoStandardCode |
P204224
|
FINISHED |
| Object | ISO 639-3 |
—
|
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 639-3 | Statement: [Yotvingian language, hasNoStandardCode, ISO 639-3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNoStandardCode Context triple: [Yotvingian language, hasNoStandardCode, ISO 639-3]
-
A.
hasStandardCode
Indicates that an entity is associated with a recognized standard code that formally identifies or classifies it.
-
B.
hasCodeA
Indicates that an entity is associated with or assigned a specific code labeled as type A.
-
C.
hasNOCCode
Indicates that an entity is associated with a specific National Occupational Classification (NOC) code that categorizes its occupation or job type.
-
D.
hasIneCode
Indicates that an entity is associated with a specific INE (national statistics or education) code that identifies it in an official registry.
-
E.
hasAssociatedStandard
Indicates that something is linked to or governed by a particular standard or set of standards.
- F. None of above. chosen
Provenance (4 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_69f76dc2b6b0819095a61debbd405269 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a034ca1a8d88190bd44f33814436e59 |
completed | May 12, 2026, 3:52 p.m. |
| PD | Predicate disambiguation | batch_6a034b591f2481908e05562841c9a3c2 |
completed | May 12, 2026, 3:46 p.m. |
| PDg | Predicate description generation | batch_6a034ca0f2808190a4eb2e1e94fcaa47 |
completed | May 12, 2026, 3:52 p.m. |
Created at: May 3, 2026, 4 p.m.