Triple
T29719774
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Curtis Institute of Music concert hall |
E752013
|
entity |
| Predicate | hostsEnsemble |
P76907
|
FINISHED |
| Object | Curtis Symphony Orchestra |
—
|
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: Curtis Symphony Orchestra | Statement: [Curtis Institute of Music concert hall, hostsEnsemble, Curtis Symphony Orchestra]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostsEnsemble Context triple: [Curtis Institute of Music concert hall, hostsEnsemble, Curtis Symphony Orchestra]
-
A.
hostOccupation
Indicates that one entity serves as the primary job, profession, or role held by another entity.
-
B.
hostArena
chosen
Indicates that one entity serves as the arena or venue where an event or activity involving the other entity takes place.
-
C.
hostStar
Indicates that one celestial object serves as the primary star around which another object, such as a planet or system, is associated or orbits.
-
D.
hostsCompany
Indicates that one entity provides space, infrastructure, or support for a company to operate, be located, or hold activities.
-
E.
hostsAward
Indicates that an entity organizes and presents an award event or ceremony for 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_69f0d628c00c8190ab5ee7e423d7ec3c |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f67d3624248190a36a9b2d2e9778d4 |
completed | May 2, 2026, 10:39 p.m. |
| PD | Predicate disambiguation | batch_69f678ce54b081908c26edfd49e39c60 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 28, 2026, 7:36 p.m.