Triple
T27051077
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | YouTube Symphony Orchestra 2009 project |
E684773
|
entity |
| Predicate | numberOfMusiciansSelected |
P20922
|
FINISHED |
| Object | approximately 90 |
—
|
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: approximately 90 | Statement: [YouTube Symphony Orchestra 2009 project, numberOfMusiciansSelected, approximately 90]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfMusiciansSelected Context triple: [YouTube Symphony Orchestra 2009 project, numberOfMusiciansSelected, approximately 90]
-
A.
numberOfMusicians
Indicates the quantity of musicians associated with a given entity or event.
-
B.
hasApproximateNumberOfMusicians
chosen
Indicates that an entity is associated with an estimated or approximate count of musicians involved with it.
-
C.
numberOfPerformers
Indicates the quantity of performers involved in a given event, act, or performance.
-
D.
numberOfInstruments
Indicates the quantitative count of instruments associated with or involved in a given entity or event.
-
E.
numberOfSoloists
Indicates the quantity of individual performers who play or sing solo parts within a given musical work, performance, or section.
- 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_69ef14829fac8190914bef9ecc3005d7 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69fe766490c081908c49c8cc07d0ae9b |
completed | May 8, 2026, 11:48 p.m. |
| PD | Predicate disambiguation | batch_69fe75bb5f4481908572a5ffcbdc5154 |
completed | May 8, 2026, 11:46 p.m. |
Created at: April 27, 2026, 8:14 a.m.