Triple
T9717254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Consualia |
E235171
|
entity |
| Predicate | associatedWithDeity |
P1481
|
FINISHED |
| Object | Consus |
E817218
|
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: Consus | Statement: [Consualia, associatedWithDeity, Consus]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Consus Context triple: [Consualia, associatedWithDeity, Consus]
-
A.
Consus
chosen
Consus is an ancient Roman deity associated with the protection of stored grain and secret counsel, often linked to agricultural festivals and underground altars.
-
B.
Togodumnus
Togodumnus was a 1st-century AD British tribal leader, likely a king of the Catuvellauni, who opposed the Roman invasion of Britain under Emperor Claudius.
-
C.
Dorus
Dorus is a figure in Greek mythology regarded as the eponymous ancestor of the Dorian people.
-
D.
Megareus
Megareus is a Theban warrior and son of Creon in Greek mythology, known for his doomed defense of Thebes during the war of the Seven Against Thebes.
-
E.
Xuthus
Xuthus is a figure in Greek mythology, traditionally regarded as a son of Hellen and a progenitor of the Ionian and Achaean Greek tribes.
- 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_69ca84cd8fa0819090a5e243ceb37003 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9e3d75e08190b4d86363595bd40d |
completed | April 1, 2026, 10:37 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d1afa6d0d08190a8008b675c9aabb1 |
completed | April 5, 2026, 12:41 a.m. |
Created at: March 30, 2026, 8:20 p.m.