Triple
T4907622
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sappho |
E109949
|
entity |
| Predicate | wroteAbout |
P2831
|
FINISHED |
| Object | Eros |
E249778
|
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: Eros | Statement: [Sappho, wroteAbout, Eros]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Eros Context triple: [Sappho, wroteAbout, Eros]
-
A.
Eros (primordial)
chosen
Eros (primordial) is an ancient Greek primordial deity embodying the fundamental force of love and procreation that brings order and cohesion to the cosmos.
-
B.
Cupid
Cupid is one of Santa Claus’s traditional flying reindeer, typically depicted pulling his sleigh on Christmas Eve.
-
C.
Cupid
Cupid is the Roman god of love and desire, traditionally depicted as a winged boy whose arrows cause people to fall in love.
-
D.
Philotes
Philotes is a minor Greek goddess personifying friendship, affection, and social bonds.
-
E.
Amor
Amor is the personification of love in Christoph Willibald Gluck’s opera "Orphée et Eurydice," often depicted as a divine figure guiding the fate of the lovers.
- 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_69bd441180708190ba42ffb44fea533a |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6e7452d481909078a0027e2a4566 |
completed | March 20, 2026, 3:57 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be6fdd89588190ae9c8de779d89aaf |
completed | March 21, 2026, 10:15 a.m. |
Created at: March 20, 2026, 1:29 p.m.