Triple
T6110206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KMIA |
E136216
|
entity |
| Predicate | languageOfCodeStandard |
P18654
|
FINISHED |
| Object | English |
—
|
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: English | Statement: [KMIA, languageOfCodeStandard, English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfCodeStandard Context triple: [KMIA, languageOfCodeStandard, English]
-
A.
languageOfCode
chosen
Indicates that a programming code artifact is written in, or uses, a particular programming language.
-
B.
languageCodeStandard
Indicates that a language code conforms to a specific standardized coding scheme (such as ISO language code standards).
-
C.
standardLanguageOf
Indicates that one entity serves as the officially recognized or commonly used standard language for another entity (such as a country, region, or organization).
-
D.
codeStandard
Indicates that an entity adheres to, complies with, or is governed by a specified coding or programming standard.
-
E.
languageOfDocumentation
Indicates the language in which the documentation for an entity is written or provided.
- 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_69c0089ea6f88190b349be53e04b4f5f |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c05b84ed088190a12cdb844d743326 |
completed | March 22, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69c049f80e2081909b7d84a104cda68d |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:13 p.m.