Triple
T17302204
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Juno Sospita |
E420064
|
entity |
| Predicate | hasRomanFestival |
P126905
|
FINISHED |
| Object | celebrations at Lanuvium |
—
|
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: celebrations at Lanuvium | Statement: [Juno Sospita, hasRomanFestival, celebrations at Lanuvium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRomanFestival Context triple: [Juno Sospita, hasRomanFestival, celebrations at Lanuvium]
-
A.
hasRomanRemains
Indicates that the subject contains or is the location of physical remains or archaeological evidence from the Roman period.
-
B.
hasRomanMonument
Indicates that one entity possesses, contains, or includes a monument of Roman origin or style.
-
C.
hasRomanName
Indicates that an entity is associated with or known by a name derived from or used in ancient Rome.
-
D.
mainRomanSanctuary
Indicates that one entity serves as the primary Roman religious sanctuary or temple associated with another entity.
-
E.
allyOfRome
Indicates a relationship where one entity is politically or militarily aligned with, and offers support or cooperation to, Rome.
- F. None of above. chosen
Provenance (4 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_69d886db32608190a61e18862c5a8af6 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e438fba938819084333764b868bd83 |
completed | April 19, 2026, 2:07 a.m. |
| PD | Predicate disambiguation | batch_69e3b0118ad08190b119cd219c68ba67 |
completed | April 18, 2026, 4:23 p.m. |
| PDg | Predicate description generation | batch_69e3b2a225b08190a50f984caa6513b9 |
completed | April 18, 2026, 4:34 p.m. |
Created at: April 10, 2026, 5:41 a.m.