Triple
T36492192
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Michigan Theater |
E899078
|
entity |
| Predicate | historicOrganStatus |
P203178
|
FINISHED |
| Object | original 1927 Barton organ |
—
|
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: original 1927 Barton organ | Statement: [Michigan Theater, historicOrganStatus, original 1927 Barton organ]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicOrganStatus Context triple: [Michigan Theater, historicOrganStatus, original 1927 Barton organ]
-
A.
historicalStatusOf
Indicates the historical condition, role, or classification that an entity held during a specific past period or context.
-
B.
historicState
Indicates that an entity was formerly a state or political entity in the past but no longer holds that status in the present.
-
C.
historicManager
Indicates that an entity previously held a managerial role or position over another entity during a past period.
-
D.
historicUsePersistsIn
Indicates that a practice, feature, or condition originating in the past continues to exist or be applied in the present.
-
E.
historicFor
Indicates that something holds historical significance or importance specifically in relation 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_69f76e5ad4588190bdbce60c52fbb785 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a013632a3048190b05716d803f34716 |
completed | May 11, 2026, 1:51 a.m. |
| PD | Predicate disambiguation | batch_6a01309582e48190a05d47d96ffb7a46 |
completed | May 11, 2026, 1:27 a.m. |
| PDg | Predicate description generation | batch_6a013631f4d48190b1e79e8ff313d3d2 |
completed | May 11, 2026, 1:51 a.m. |
Created at: May 3, 2026, 4:10 p.m.