Triple
T14395745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shtokavian dialect |
E356943
|
entity |
| Predicate | hasNameOriginFromWord |
P64092
|
FINISHED |
| Object | što |
—
|
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: što | Statement: [Shtokavian dialect, hasNameOriginFromWord, što]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNameOriginFromWord Context triple: [Shtokavian dialect, hasNameOriginFromWord, što]
-
A.
hasNameOrigin
Indicates that the origin or source of an entity’s name is specified by the related entity.
-
B.
possibleNameEtymology
chosen
Indicates a hypothesized or suggested origin or derivation of an entity’s name from another term, source, or linguistic root.
-
C.
hasNameOriginType
Indicates that there is a specific type or category describing the origin of an entity’s name.
-
D.
hasAcronymOrigin
Indicates that an acronym is derived from or originates from a specific longer expression or name.
-
E.
etymologicalRootName
Indicates that one name is derived from, or originates etymologically in, another name.
- 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_69d827927c988190ad98bb0360981783 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de90826f908190b3969af9b7cf922f |
completed | April 14, 2026, 7:07 p.m. |
| PD | Predicate disambiguation | batch_69de2aa024c48190805df6a9d63deb10 |
completed | April 14, 2026, 11:53 a.m. |
Created at: April 10, 2026, 1:17 a.m.