Triple
T13852529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Δίας |
E332979
|
entity |
| Predicate | ανήκειΣεΓένος |
P13151
|
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: [Δίας, ανήκειΣεΓένος, Τιτάνες (καταγωγή από Τιτάνες)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ανήκειΣεΓένος Context triple: [Δίας, ανήκειΣεΓένος, Τιτάνες (καταγωγή από Τιτάνες)]
-
A.
hadEponymousAncestor
Indicates that an entity has an ancestor whose name it shares or from whom its own name is derived.
-
B.
ancestor
Indicates that one entity is a forebear of another in a lineage, occurring in an earlier generation and connected through one or more parent-child relationships.
-
C.
gens
Indicates a relationship where one entity generates, produces, or gives rise to another entity.
-
D.
tribeOrGens
chosen
Indicates a relationship where an entity belongs to, is associated with, or is identified as a particular tribe or gens (clan/lineage group).
-
E.
denotesGeneration
Indicates that one entity originates, produces, or gives rise to another entity, establishing a generative or causal source-result relationship between them.
- 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_69d81c5ba13c8190839315f54768acfd |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de02da9460819093a3ec5a3c62ea81 |
completed | April 14, 2026, 9:03 a.m. |
| PD | Predicate disambiguation | batch_69dbc8691b608190a25a7c70a366b170 |
completed | April 12, 2026, 4:29 p.m. |
Created at: April 9, 2026, 10:14 p.m.