Triple
T4101436
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman Theatre (Amman) |
E87948
|
entity |
| Predicate | lowerTierName |
P53373
|
FINISHED |
| Object | ima 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: ima cavea | Statement: [Roman Theatre (Amman), lowerTierName, ima cavea]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lowerTierName Context triple: [Roman Theatre (Amman), lowerTierName, ima cavea]
-
A.
hasLowerTier
Indicates that one entity is ranked, valued, or classified at a lower level or tier relative to another entity.
-
B.
lowerRank
Indicates that one entity holds an inferior or subordinate rank, status, or position relative to another entity.
-
C.
lowerCourseName
Indicates that the course’s name is represented in all lowercase characters.
-
D.
lowerLevelUsedFor
Indicates that a lower-level component, resource, or abstraction is utilized to implement, support, or realize the functionality of a higher-level one.
-
E.
lowerLocation
Indicates that one entity is located physically below or at a lower vertical position relative to another entity.
- 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_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. |
| PDg | Predicate description generation | batch_69aefa5c52648190b001027f4dba75cb |
completed | March 9, 2026, 4:50 p.m. |
Created at: March 9, 2026, 3:40 p.m.