Triple
T16383858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amphitheatre of El Jem |
E397872
|
entity |
| Predicate | oneOfLargestRomanAmphitheatres |
P123182
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Amphitheatre of El Jem, oneOfLargestRomanAmphitheatres, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oneOfLargestRomanAmphitheatres Context triple: [Amphitheatre of El Jem, oneOfLargestRomanAmphitheatres, true]
-
A.
amphitheatreInstanceOf
Indicates that an entity is classified as, or is an instance of, an amphitheatre.
-
B.
mainRomanSanctuary
Indicates that one entity serves as the primary Roman religious sanctuary or temple associated with another entity.
-
C.
amphitheatreBuiltUnder
Indicates that an amphitheatre was constructed during the rule, authority, or administration of a specified person or governing entity.
-
D.
allyOfRome
Indicates a relationship where one entity is politically or militarily aligned with, and offers support or cooperation to, Rome.
-
E.
pantheon
Indicates a relationship where a group of deities collectively belong to or are recognized within the same religious or mythological system.
- 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_69d87f2880b48190ae1a9673a3bbef80 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e319de83248190b5d43646fa9b6cda |
completed | April 18, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69e226f94dd48190b7b8e0e983738a67 |
completed | April 17, 2026, 12:26 p.m. |
| PDg | Predicate description generation | batch_69e24555bb6c8190977cf5c5f9149056 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 10, 2026, 5:08 a.m.