Triple
T5414663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elissa |
E121100
|
entity |
| Predicate | spouse |
P13
|
FINISHED |
| Object | Acerbas |
E481165
|
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: Acerbas | Statement: [Elissa, spouse, Acerbas]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Acerbas Context triple: [Elissa, spouse, Acerbas]
-
A.
Acerbas
chosen
Acerbas, also known as Sychaeus, is a wealthy Tyrian priest in classical mythology whose murder leads his wife Dido to flee and ultimately found Carthage.
-
B.
Arremon
Arremon is a genus of Neotropical sparrow-like birds known for their distinctive head patterns and association with forest undergrowth.
-
C.
Ateso
Ateso is a Nilotic language spoken primarily by the Teso people of eastern Uganda and western Kenya.
-
D.
Aternus
Aternus is an ancient river in central Italy historically associated with the territory of the Marrucini people.
-
E.
Aletes
Aletes is a figure from Greek mythology, traditionally regarded as a descendant of Heracles and associated with the royal lineage that ruled parts of the Peloponnese.
- 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_69bd463a41cc8190b32ff5af2b96ca93 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd87bcace08190932fe85e4b4aeffc |
completed | March 20, 2026, 5:45 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bf3aa743008190840ddcea08d67a66 |
completed | March 22, 2026, 12:41 a.m. |
Created at: March 20, 2026, 2:05 p.m.