Triple
T9954037
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aztec Theater façade |
E195400
|
entity |
| Predicate | recursThroughoutSeries |
P54121
|
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: [Aztec Theater façade, recursThroughoutSeries, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recursThroughoutSeries Context triple: [Aztec Theater façade, recursThroughoutSeries, true]
-
A.
seriesOf
Indicates that one entity is a sequence or ordered set of related items, events, or parts that collectively form or belong to another entity.
-
B.
hasRecurringSeriesProtagonists
Indicates that a recurring series features one or more protagonists who appear repeatedly across its installments.
-
C.
formerSeries
Indicates that one entity was previously a series associated with another entity, but no longer holds that status.
-
D.
isSeriesOf
Indicates that one entity is a sequence or set of related items that collectively form a series associated with another entity.
-
E.
recursIn
chosen
Indicates that an event, pattern, or entity appears repeatedly or returns multiple times within a given context, sequence, or timeframe.
- 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.