Triple
T6144543
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Temple of Juno Moneta |
E137042
|
entity |
| Predicate | associatedRoleOfDeity |
P9987
|
FINISHED |
| Object | protector of the Roman state |
—
|
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: protector of the Roman state | Statement: [Temple of Juno Moneta, associatedRoleOfDeity, protector of the Roman state]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedRoleOfDeity Context triple: [Temple of Juno Moneta, associatedRoleOfDeity, protector of the Roman state]
-
A.
relatedNameOfGod
Indicates that one entity is a name, title, or designation that refers to or is associated with God.
-
B.
attributeOfDeity
Indicates that something is a characteristic, quality, or property belonging to a deity.
-
C.
relationshipToDeities
Indicates how an entity is connected or related to one or more deities, such as through worship, lineage, role, or status.
-
D.
associatedReligionRole
Indicates that one entity holds a specific religious role, office, or function in relation to another entity.
-
E.
mythologicalRole
chosen
Indicates the specific function, duty, or status an entity holds within a mythological or legendary context.
- 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_69c008a2c6308190a56519b22d55d083 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05cb645508190aea2d77c9de174ba |
completed | March 22, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69c055f39e0881909ae56444b1b48929 |
completed | March 22, 2026, 8:49 p.m. |
Created at: March 22, 2026, 4:16 p.m.