Triple
T4101434
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman Theatre (Amman) |
E87948
|
entity |
| Predicate | upperTierName |
P37954
|
FINISHED |
| Object | summa cavea |
—
|
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: summa cavea | Statement: [Roman Theatre (Amman), upperTierName, summa cavea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: upperTierName Context triple: [Roman Theatre (Amman), upperTierName, summa cavea]
-
A.
hasUpperTier
Indicates that one entity occupies a higher or superior level, rank, or layer in a hierarchical structure relative to another entity.
-
B.
higherTierAuthority
Indicates that one entity holds a superior or higher-ranking level of authority or control over another entity.
-
C.
hasTierName
chosen
Indicates that an entity is associated with a specific tier by its name.
-
D.
firstTier
Indicates that one entity occupies the highest or primary level, rank, or priority relative to others in a hierarchical structure.
-
E.
higherTitleOf
Indicates that one entity holds a job or position title that is hierarchically superior to the title held by another entity.
- 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_69aed94564cc8190a9c1457daedb6e7f |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefd0ed168819093c83ba079d6725c |
completed | March 9, 2026, 5:02 p.m. |
| PD | Predicate disambiguation | batch_69aef90b2ef08190ae84febfd69dd48b |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:40 p.m.