Triple
T9954046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aztec Theater façade |
E195400
|
entity |
| Predicate | hasScreenRole |
P76157
|
FINISHED |
| Object | background location |
—
|
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: background location | Statement: [Aztec Theater façade, hasScreenRole, background location]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasScreenRole Context triple: [Aztec Theater façade, hasScreenRole, background location]
-
A.
hasScreen
Indicates that an entity is equipped with or includes a screen or display component.
-
B.
hasSectionRole
Indicates that an entity holds a specific role or function within a particular section or subdivision of a larger structure or context.
-
C.
hasBorderRole
Indicates that an entity holds a specific functional or administrative role related to a border or boundary between regions or jurisdictions.
-
D.
hasSettingRole
chosen
Indicates that an entity participates in a setting by fulfilling a specific contextual or functional role within it.
-
E.
hasAria
Indicates that one entity possesses, contains, or is associated with an aria (a specific vocal piece or melodic section).
- 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_69ca82eaaa008190a54fa1a9f954b9ad |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb694b95481909d049302818e7137 |
completed | April 2, 2026, 12:21 a.m. |
| PD | Predicate disambiguation | batch_69cd1d97c44081908730071269f07712 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:46 p.m.