Triple
T1556366
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Banda languages |
E33212
|
entity |
| Predicate | ISO639-3CollectiveCode |
P6525
|
FINISHED |
| Object | bad |
—
|
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: bad | Statement: [Central Banda languages, ISO639-3CollectiveCode, bad]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ISO639-3CollectiveCode Context triple: [Central Banda languages, ISO639-3CollectiveCode, bad]
-
A.
ISO639Scope
Indicates the classification of a language according to its scope, such as whether it represents an individual language, a macrolanguage, or a collection of languages.
-
B.
ISO639Macrolanguage
Indicates that a language variety is part of a broader ISO 639-defined macrolanguage grouping that encompasses multiple closely related individual languages.
-
C.
ISO639_3Status
chosen
Indicates the classification or status assigned to a language according to the ISO 639-3 standard (e.g., active, extinct, historical, constructed).
-
D.
ISO639Status
Indicates the classification of a language’s status according to the ISO 639 standard (e.g., whether and how it is recognized or coded in that system).
-
E.
languageCodeISO639-2
Indicates that an entity is associated with a language identified by its ISO 639-2 three-letter code.
- 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_69a885ef9cf48190b0af0f5ce3d02231 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a9407d9d1481909597af97b16512cc |
completed | March 5, 2026, 8:36 a.m. |
| PD | Predicate disambiguation | batch_69a907b688d081908171f89010c53973 |
completed | March 5, 2026, 4:33 a.m. |
Created at: March 4, 2026, 7:27 p.m.