Triple
T31908822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jevanic |
E814624
|
entity |
| Predicate | grammarRelation |
P172723
|
FINISHED |
| Object | shares much of its grammar with Greek |
—
|
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: shares much of its grammar with Greek | Statement: [Jevanic, grammarRelation, shares much of its grammar with Greek]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: grammarRelation Context triple: [Jevanic, grammarRelation, shares much of its grammar with Greek]
-
A.
semanticRelation
Indicates a general meaning-based connection between two entities, such as similarity, implication, or conceptual association.
-
B.
ridgeRelation
Indicates a relationship in which one entity is a ridge or forms a ridge-like structural feature relative to another entity.
-
C.
datumRelation
Indicates a relationship where one piece of data is connected to, derived from, or otherwise associated with another piece of data.
-
D.
symbolicRelation
Indicates a relationship where one entity stands for, represents, or conveys meaning about another through symbols or abstract signs.
-
E.
stepRelation
Indicates a relationship where one entity is a step-relative of another, such as a stepparent, stepchild, or stepsibling connection.
- 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_69f348f109d88190b5005372c53d2fcd |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b1b92b9081909105e14626a3c04b |
completed | May 3, 2026, 2:23 a.m. |
| PD | Predicate disambiguation | batch_69f6aca59d4881908d14ed47962703bd |
completed | May 3, 2026, 2:02 a.m. |
| PDg | Predicate description generation | batch_69f6af7d92008190aead47eaae8cc091 |
completed | May 3, 2026, 2:14 a.m. |
Created at: May 1, 2026, 12:01 a.m.