Triple
T4144008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Serbian Latin alphabet |
E89339
|
entity |
| Predicate | hasDigraph |
P54131
|
FINISHED |
| Object | Dž |
—
|
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: Dž | Statement: [Serbian Latin alphabet, hasDigraph, Dž]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDigraph Context triple: [Serbian Latin alphabet, hasDigraph, Dž]
-
A.
usesDigraph
Indicates that one entity employs or represents information using a directed graph structure, where relationships have a specified direction.
-
B.
hasCombiningMarks
Indicates that an entity (such as a character or string) includes one or more combining marks attached to a base element.
-
C.
hasLigatures
Indicates that one writing system, font, or text includes combined character forms (ligatures) that join two or more individual glyphs into a single symbol.
-
D.
hasConsonantSigns
Indicates that one entity possesses or includes consonant sign characters as part of its representation or structure.
-
E.
usesDiacritics
Indicates that the referenced text or linguistic element employs diacritical marks as part of its written form.
- 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_69aed95785788190ae75bcf0cd1cafdf |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af03a0f3408190adba7a8513bd3d12 |
completed | March 9, 2026, 5:30 p.m. |
| PD | Predicate disambiguation | batch_69af018a54848190987f18c066c75068 |
completed | March 9, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69af039fb19c8190b20e62a3b3ad25c1 |
completed | March 9, 2026, 5:30 p.m. |
Created at: March 9, 2026, 3:43 p.m.