Triple
T25823350
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ljudevit Gaj |
E650457
|
entity |
| Predicate | introducedLetter |
P513
|
FINISHED |
| Object | č |
—
|
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: č | Statement: [Ljudevit Gaj, introducedLetter, č]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedLetter Context triple: [Ljudevit Gaj, introducedLetter, č]
-
A.
letterRepresents
Indicates that a particular letter or character stands for, symbolizes, or denotes a specific value, concept, or entity.
-
B.
firstLetter
Indicates that one entity is the initial character or starting letter of another entity (typically a string or word).
-
C.
introducedByCharacters
Indicates that something (such as an idea, object, or event) is brought into the narrative or context by specific characters.
-
D.
introduced
chosen
Indicates that one entity caused another entity to become known, presented, or brought into use for the first time to a person, group, or context.
-
E.
usesSpecialLetterFor
Indicates that one entity employs a particular special letter or character specifically in relation to another entity.
- 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_69f6691f5e188190b12c7b2eb729a45e |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f66598d6008190a7ca8ff80399fd34 |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 22, 2026, 7:31 a.m.