Triple
T4355360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alabama Theatre |
E98133
|
entity |
| Predicate | renovationType |
P24756
|
FINISHED |
| Object | restoration |
—
|
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: restoration | Statement: [Alabama Theatre, renovationType, restoration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: renovationType Context triple: [Alabama Theatre, renovationType, restoration]
-
A.
renovationPurpose
Indicates that an entity is being renovated with a specific intended goal, use, or outcome in mind.
-
B.
renovationFeature
Indicates that an entity has a specific renovation-related characteristic, element, or improvement associated with it.
-
C.
renovationResult
chosen
Indicates the outcome or state produced by a renovation process, linking the renovation activity to its resulting condition or product.
-
D.
hasRenovation
Indicates that an entity has undergone, is undergoing, or is associated with a renovation process or renovation event.
-
E.
architectOfRenovation
Indicates that one entity is the architect responsible for designing or overseeing the renovation of 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_69b3454965f881908c41190bb22f0e4b |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b351c5773481908446d84897e7a533 |
completed | March 12, 2026, 11:52 p.m. |
| PD | Predicate disambiguation | batch_69b34f51ed7c8190b7bf5f44b56b730d |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:16 p.m.