Triple
T31146963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regio XIV Transtiberim |
E793950
|
entity |
| Predicate | containedSanctuary |
P180259
|
FINISHED |
| Object | Temple of Fors Fortuna |
—
|
NE NERFINISHED |
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: Temple of Fors Fortuna | Statement: [Regio XIV Transtiberim, containedSanctuary, Temple of Fors Fortuna]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containedSanctuary Context triple: [Regio XIV Transtiberim, containedSanctuary, Temple of Fors Fortuna]
-
A.
sanctumContains
Indicates that one sanctum or sacred space physically or conceptually includes or holds another entity within its bounds.
-
B.
hasSanctuary
Indicates that one entity provides or serves as a place of refuge, protection, or safe haven for another entity.
-
C.
hadSanctuaryOf
Indicates that an entity possessed or hosted a sanctuary dedicated to another entity.
-
D.
involvesSanctuary
Indicates that an action, event, or relationship includes or takes place within a sanctuary or protected refuge.
-
E.
hasSanctuaryIn
chosen
Indicates that an entity maintains or possesses a sanctuary located within a specified place or region.
- 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_69f224d41bb48190a5621cd1485e3a30 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69ff5285ed74819097e6e2a9084a079a |
completed | May 9, 2026, 3:28 p.m. |
| PD | Predicate disambiguation | batch_69ff51fbe28881908ac8417dff9db81a |
completed | May 9, 2026, 3:25 p.m. |
Created at: April 29, 2026, 9:06 p.m.