Triple
T24479235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ga language |
E617320
|
entity |
| Predicate | ISO 639-1 code |
P110016
|
FINISHED |
| Object | none |
—
|
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: none | Statement: [Ga language, ISO 639-1 code, none]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ISO 639-1 code Context triple: [Ga language, ISO 639-1 code, none]
-
A.
ISO639-1CodeFor
chosen
Indicates that one entity is the ISO 639-1 two-letter language code corresponding to the language represented by the other entity.
-
B.
ISO639-1Equivalent
Indicates that two language identifiers are equivalent according to the ISO 639-1 two-letter language code standard.
-
C.
ISO3166-1Code
Indicates the standardized two- or three-letter country or territory code assigned under the ISO 3166-1 international standard.
-
D.
ISO639Language
Indicates that an entity is associated with a language identified or classified according to the ISO 639 language code standard.
-
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_69e2d7f3ae788190b683394db15f220e |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f29ed3fce88190b5be7e085ef88c97 |
completed | April 30, 2026, 12:14 a.m. |
| PD | Predicate disambiguation | batch_69f287d76c7c81909494f12e606a9149 |
completed | April 29, 2026, 10:36 p.m. |
Created at: April 18, 2026, 2:21 a.m.