Triple
T11624396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Temple of Jupiter (Pompeii) |
E276223
|
entity |
| Predicate | useBefore79CE |
P100640
|
FINISHED |
| Object | principal temple of the city |
—
|
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: principal temple of the city | Statement: [Temple of Jupiter (Pompeii), useBefore79CE, principal temple of the city]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: useBefore79CE Context triple: [Temple of Jupiter (Pompeii), useBefore79CE, principal temple of the city]
-
A.
introducedBefore
Indicates that one entity was introduced or presented earlier in time than another entity.
-
B.
usedBefore
Indicates that one entity was utilized or applied prior to the use or occurrence of another entity.
-
C.
isObsoleteFor
Indicates that something is no longer current, valid, or in use for a particular entity, context, or purpose.
-
D.
controlledBefore
Indicates that one entity had control or authority over another entity during a time period that occurred earlier than a specified reference time or event.
-
E.
isAncient
Indicates that the entity existed or originated in a very distant past, typically far earlier than the commonly referenced historical period.
- 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_69d6aafa51148190ab84940694c00235 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a12416908190ac2dcd7f7ebb308f |
completed | April 10, 2026, 7:05 a.m. |
| PD | Predicate disambiguation | batch_69d85dd6503c819081f9045e9d5c4f3f |
completed | April 10, 2026, 2:17 a.m. |
| PDg | Predicate description generation | batch_69d87f2e67108190ac36bf47aac12fa8 |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 8, 2026, 9:39 p.m.