Triple
T21488093
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pittsburgh Symphony Orchestra |
E530165
|
entity |
| Predicate | permanentStatusFrom |
P144564
|
FINISHED |
| Object | 1906 |
—
|
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: 1906 | Statement: [Pittsburgh Symphony Orchestra, permanentStatusFrom, 1906]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: permanentStatusFrom Context triple: [Pittsburgh Symphony Orchestra, permanentStatusFrom, 1906]
-
A.
laterStatus
Indicates that one entity represents a subsequent or resulting status or condition of another entity in time.
-
B.
customStatus
Indicates that an entity has a user-defined or non-standard status assigned to it.
-
C.
primaryStatus
Indicates the main or most important status assigned to an entity among potentially multiple statuses.
-
D.
legalStatusBefore
Indicates the legal condition or classification that applied to an entity prior to a specified event, change, or point in time.
-
E.
canonicalStatus
Indicates the formal or official standing of an entity within an established authoritative or normative system.
- 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_69e0c45acc3881908e38d3f28964152b |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9ea390bd88190bc444e6af275f6e8 |
completed | April 23, 2026, 9:45 a.m. |
| PD | Predicate disambiguation | batch_69e631f6e68081908f5ee4ce7413803e |
completed | April 20, 2026, 2:02 p.m. |
| PDg | Predicate description generation | batch_69e6386c5a4481909c37f7de7e9fc025 |
completed | April 20, 2026, 2:30 p.m. |
Created at: April 16, 2026, 6:22 p.m.