Triple
T25823349
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ljudevit Gaj |
E650457
|
entity |
| Predicate | scriptReformed |
P5211
|
FINISHED |
| Object | Croatian Latin alphabet |
—
|
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: Croatian Latin alphabet | Statement: [Ljudevit Gaj, scriptReformed, Croatian Latin alphabet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scriptReformed Context triple: [Ljudevit Gaj, scriptReformed, Croatian Latin alphabet]
-
A.
scriptAfterReform
chosen
Indicates that one script or writing system is used after a reform or modification has been applied to another script.
-
B.
formerScript
Indicates that an entity previously served as the script or writing system for another entity, but is no longer used in that role.
-
C.
furtherReformedBy
Indicates that an existing reform, change, or modification to something is subsequently revised, extended, or improved by another agent or process.
-
D.
scripturalFunction
Indicates the role or purpose that a text or passage serves within a scriptural or religious context.
-
E.
functionAfterReformation
Indicates that one function or role exists or is performed in the state or period following a process of reformation or reform.
- 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_69e7ab367fcc8190a5ff1e7f3da046a4 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6135293908190809e255bf6334760 |
completed | May 2, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_69f611a72780819082f44e66ca2c6ac9 |
completed | May 2, 2026, 3 p.m. |
Created at: April 22, 2026, 7:31 a.m.