Triple
T31278504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Temple of Sancus |
E797592
|
entity |
| Predicate | dedicationAspect |
P36403
|
FINISHED |
| Object | oaths of loyalty |
—
|
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: oaths of loyalty | Statement: [Temple of Sancus, dedicationAspect, oaths of loyalty]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dedicationAspect Context triple: [Temple of Sancus, dedicationAspect, oaths of loyalty]
-
A.
dedicationBy
Indicates that one entity formally dedicates, commits, or devotes another entity (such as a work, resource, or effort) to a particular person, purpose, or cause.
-
B.
dedicationType
chosen
Indicates the specific kind or category of dedication that characterizes the relationship or action between entities.
-
C.
inspiredDedicationOf
Indicates that one entity’s dedication, commitment, or devoted effort is motivated, sparked, or strengthened by another entity.
-
D.
dedicationAspectOfJuno
Indicates that the dedication specifically concerns an aspect, epithet, or particular manifestation of the deity Juno.
-
E.
usedAsDedicationFor
Indicates that something (such as a work, object, or act) is dedicated in honor of, or specifically intended for, another entity.
- 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_69f224def9088190a37034eab3daf57f |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6b21e7e088190832a3db585daea1c |
completed | May 3, 2026, 2:25 a.m. |
| PD | Predicate disambiguation | batch_69f6b14faf608190a25b977c0740729c |
completed | May 3, 2026, 2:22 a.m. |
Created at: April 29, 2026, 9:13 p.m.