Triple
T37388324
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Free Trade Hall |
E928632
|
entity |
| Predicate | notableResidentOrchestra |
P205878
|
FINISHED |
| Object | Hallé Orchestra |
E272221
|
NE 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: Hallé Orchestra | Statement: [Free Trade Hall, notableResidentOrchestra, Hallé Orchestra]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableResidentOrchestra Context triple: [Free Trade Hall, notableResidentOrchestra, Hallé Orchestra]
-
A.
notableEnsemble
Indicates that an entity is a prominent or significant member of a particular group, band, or ensemble.
-
B.
notableConductor
Indicates that the subject is a conductor who is recognized as notable or distinguished in their field.
-
C.
featuresOrchestraLedBy
Indicates that something (such as a work, event, or recording) includes an orchestra whose performance is directed or led by a specified conductor.
-
D.
notableQuartet
Indicates that the four associated entities together form a notable or distinguished quartet.
-
E.
associatedNationalityOfOrchestra
Indicates that an orchestra is linked to or identified with a particular nationality or country.
- F. None of above. chosen
Provenance (5 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_69f76ebb10c481909b54b9dba263e29f |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a40951fea748190a5fc795dc7479ff4 |
completed | June 28, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_6a037a13a1308190a202df66f4781855 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c842b2c819082f1d2db995ac2eb |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:16 p.m.