Triple
T21488089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pittsburgh Symphony Orchestra |
E530165
|
entity |
| Predicate | shortName |
P43
|
FINISHED |
| Object | PSO |
—
|
NE NERFINISHED |
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: PSO | Statement: [Pittsburgh Symphony Orchestra, shortName, PSO]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: PSO Context triple: [Pittsburgh Symphony Orchestra, shortName, PSO]
-
A.
PSO
chosen
PSO is a major American orchestra based in Pittsburgh, renowned for its high artistic standards and international touring and recording.
-
B.
PSO
PSO is the Public Safety Office within the Texas Governor’s Office that oversees and supports statewide public safety, criminal justice, and homeland security initiatives.
-
C.
PSO
PSO is the station code for Perris–South station, a commuter rail stop in Perris, California.
-
D.
MOEA
MOEA is Taiwan’s central government ministry responsible for formulating and implementing national economic, industrial, trade, and energy policies.
-
E.
PSI
PSI is the acronym commonly used for the Italian Socialist Party, a historic socialist political party in Italy.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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. |
Created at: April 16, 2026, 6:22 p.m.