Triple
T15651561
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Igboid |
E376323
|
entity |
| Predicate | hasISO639LanguageCodeForMajorLanguage |
P119606
|
FINISHED |
| Object | ig |
—
|
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: ig | Statement: [Igboid, hasISO639LanguageCodeForMajorLanguage, ig]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasISO639LanguageCodeForMajorLanguage Context triple: [Igboid, hasISO639LanguageCodeForMajorLanguage, ig]
-
A.
hasISO639MacrolanguageCode
Indicates that a language entity is associated with a specific ISO 639 macrolanguage code that represents a broader language grouping.
-
B.
includesMajorLanguageFamily
Indicates that one entity encompasses, contains, or is associated with a major language family as part of its scope or classification.
-
C.
hasISO6393Code
Indicates that a language or linguistic entity is associated with a specific ISO 639-3 three-letter language code.
-
D.
hasISO639_5Code
Indicates that a language or language group is associated with a specific ISO 639-5 code that identifies it within the ISO 639-5 language classification standard.
-
E.
hasWritingSystemForMajorLanguage
Indicates that there exists a writing system used to represent a major language associated with the given entity.
- 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_69d85cd1564c8190991adda63bfab4b0 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04eeed2d48190a7a8a618d90012d0 |
completed | April 16, 2026, 2:52 a.m. |
| PD | Predicate disambiguation | batch_69deda890140819082608931e993dd61 |
completed | April 15, 2026, 12:23 a.m. |
| PDg | Predicate description generation | batch_69dff7f3016c8190ac68d76e65e07af4 |
completed | April 15, 2026, 8:41 p.m. |
Created at: April 10, 2026, 4:15 a.m.