Triple
T12227157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Telamon |
E291382
|
entity |
| Predicate | childOf |
P120
|
FINISHED |
| Object | Endeïs |
E550358
|
NE 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: Endeïs | Statement: [Telamon, childOf, Endeïs]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Endeïs Context triple: [Telamon, childOf, Endeïs]
-
A.
Endeis
chosen
Endeis is a figure in Greek mythology known primarily as the mother of the hero Peleus and grandmother of Achilles.
-
B.
Enodia
Enodia is an epithet of the Greek goddess Hecate that emphasizes her role as a protector and guide along roads, thresholds, and liminal spaces.
-
C.
Enide
Enide is a heroine of Arthurian romance, best known as the loyal and courageous wife of the knight Erec in medieval French literature.
-
D.
Ende
Ende is a coastal town and regency capital on the Indonesian island of Flores, known as a regional hub and gateway to nearby natural attractions.
-
E.
Erista
Erista is the internal codename for Nvidia’s original Tegra X1 system-on-chip, notably used in the first-generation Nintendo Switch.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d6ab668acc8190963ba424049d6aee |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d91ca2101c8190955c36704935036a |
completed | April 10, 2026, 3:52 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f60aa9023881909f8373e02d2cad4b |
completed | May 2, 2026, 2:31 p.m. |
Created at: April 8, 2026, 9:51 p.m.