Triple
T27864400
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO 639-5: bnt |
E704315
|
entity |
| Predicate | hasIndividualLanguageCodesIn |
P13919
|
FINISHED |
| Object | ISO 639-3 |
—
|
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: ISO 639-3 | Statement: [ISO 639-5: bnt, hasIndividualLanguageCodesIn, ISO 639-3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIndividualLanguageCodesIn Context triple: [ISO 639-5: bnt, hasIndividualLanguageCodesIn, ISO 639-3]
-
A.
hasLinguisticCode
chosen
Indicates that an entity is associated with a specific linguistic identifier or code (such as a language or script code) that characterizes its linguistic properties.
-
B.
hasLanguageCodeScope
Indicates that a language code is valid or applicable only within a specified scope, context, or domain.
-
C.
hasLanguages
Indicates that an entity is associated with one or more languages it uses, supports, or is expressed in.
-
D.
hasLanguageInCountry
Indicates that a particular language is used or recognized within a specified country.
-
E.
hasLanguageRepresentation
Indicates that an entity is expressed, encoded, or represented using a particular natural or formal language.
- 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_69ef840f12408190b539d00d79658abf |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69fd553d7cb881908d243e7a9f30ac85 |
completed | May 8, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69fd514dcb1c81908333c70d7edd79c9 |
completed | May 8, 2026, 2:58 a.m. |
Created at: April 27, 2026, 6:20 p.m.