Triple
T34210072
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elagabal temple on the Palatine |
E877628
|
entity |
| Predicate | overlooked |
P1323
|
FINISHED |
| Object | Roman Forum |
—
|
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: Roman Forum | Statement: [Elagabal temple on the Palatine, overlooked, Roman Forum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: overlooked Context triple: [Elagabal temple on the Palatine, overlooked, Roman Forum]
-
A.
overlooks
chosen
Indicates that one entity has a view toward or looks out over another entity, typically from a higher or adjacent position.
-
B.
neglects
Indicates a relationship where one party fails to give appropriate attention, care, or consideration to another party or responsibility.
-
C.
ignoredBy
Indicates that one entity does not pay attention or respond to another entity.
-
D.
isOverlookedBy
Indicates that one entity has a view over or looks down upon another entity from a higher or vantage position.
-
E.
over
Indicates that one entity is positioned higher than and extending across or above another entity, often covering or spanning it.
- 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_69f349b0b4bc819088c1552424089ee9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71054384481908897507876233248 |
completed | May 3, 2026, 9:07 a.m. |
| PD | Predicate disambiguation | batch_69f70f3c5bfc81908585f52e196dafe5 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:55 a.m.