Triple
T9146980
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Serbo-Croatian |
E219480
|
entity |
| Predicate | usesWritingConvention |
P67410
|
FINISHED |
| Object | phonemic orthography |
—
|
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: phonemic orthography | Statement: [Serbo-Croatian, usesWritingConvention, phonemic orthography]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesWritingConvention Context triple: [Serbo-Croatian, usesWritingConvention, phonemic orthography]
-
A.
conventionFor
Indicates a relationship where something serves as a standard, rule, or customary practice governing how another thing is done, represented, or interpreted.
-
B.
hasOrthographicConvention
chosen
Indicates that there is a specific writing or spelling convention that governs how something is represented in written form.
-
C.
typingDiscipline
Indicates how a programming language enforces and manages type rules for its values and expressions.
-
D.
willWrittenIn
Indicates that a legal will was authored, drafted, or formally written in a specified location or jurisdiction.
-
E.
logicConvention
Indicates a relationship where entities participate in or are associated with a convention, event, or standard related to logic or logical systems.
- 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_69ca83e121dc81909912bd66953081c5 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca918a3c881909c34a6a682eb2625 |
completed | April 1, 2026, 5:11 a.m. |
| PD | Predicate disambiguation | batch_69cc6603ce8c8190bf6e8d6754bdec54 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:20 p.m.