Triple
T34279310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ISO 639-3 |
E879548
|
entity |
| Predicate | definesCodeFor |
P112418
|
FINISHED |
| Object | Yakan language |
—
|
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: Yakan language | Statement: [ISO 639-3, definesCodeFor, Yakan language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesCodeFor Context triple: [ISO 639-3, definesCodeFor, Yakan language]
-
A.
codeFor
Indicates that one entity serves as the implementation, encoding, or programmatic representation for another entity.
-
B.
codifiedFor
Indicates that something has been formally organized, standardized, or written down specifically for use by or application to another entity.
-
C.
codeForLanguage
Indicates that a piece of code is written in, or intended to be executed by, a particular programming or markup language.
-
D.
codeForSystem
chosen
Indicates that something serves as the code, identifier, or encoding used within or by a particular system.
-
E.
designCode
Indicates that one entity creates, specifies, or defines the design or coding scheme used by another entity.
- 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_69f349b5f6648190b9420d94a4cd16e0 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fe7eb4b8348190bb19d35766189ed4 |
completed | May 9, 2026, 12:24 a.m. |
| PD | Predicate disambiguation | batch_69fe7c35d2148190ab952e54feda1e76 |
completed | May 9, 2026, 12:13 a.m. |
Created at: May 1, 2026, 1:57 a.m.