Triple
T4407322
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dii Consentes |
E93765
|
entity |
| Predicate | pantheonRole |
P27705
|
FINISHED |
| Object | principal deities |
—
|
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: principal deities | Statement: [Dii Consentes, pantheonRole, principal deities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pantheonRole Context triple: [Dii Consentes, pantheonRole, principal deities]
-
A.
pantheonIncludes
Indicates that a particular deity, figure, or entity is a member of, or belongs to, a specified pantheon.
-
B.
positionInPantheon
chosen
Indicates the rank, role, or hierarchical standing that a deity or figure holds within a specific pantheon or religious hierarchy.
-
C.
pantheon
Indicates a relationship where a group of deities collectively belong to or are recognized within the same religious or mythological system.
-
D.
roleInTheology
Indicates the specific function, position, or significance an entity holds within a theological system, doctrine, or belief framework.
-
E.
hasPantheonName
Indicates that an entity is associated with a specific pantheon and is identified by the given pantheon name.
- 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_69b345158c748190a2c040fce2da9980 |
completed | March 12, 2026, 10:58 p.m. |
| NER | Named-entity recognition | batch_69b3548b1ca08190b3136867c7098d86 |
completed | March 13, 2026, 12:04 a.m. |
| PD | Predicate disambiguation | batch_69b34f5b36a881909bf2e970aa523390 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:28 p.m.