Triple
T25701211
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Starting Here, Starting Now |
E644466
|
entity |
| Predicate | hasNumberOfPerformers |
P84129
|
FINISHED |
| Object | small ensemble cast |
—
|
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: small ensemble cast | Statement: [Starting Here, Starting Now, hasNumberOfPerformers, small ensemble cast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNumberOfPerformers Context triple: [Starting Here, Starting Now, hasNumberOfPerformers, small ensemble cast]
-
A.
numberOfPerformers
chosen
Indicates the quantity of performers involved in a given event, act, or performance.
-
B.
numberOfMainPerformers
Indicates the count of primary performers involved in a performance or event.
-
C.
approximateNumberOfPerformers
Indicates an estimated count of performers involved in an event or performance.
-
D.
typicalPerformerCount
Indicates the usual or standard number of performers involved in carrying out the associated activity or event.
-
E.
hasApproximateNumberOfMusicians
Indicates that an entity is associated with an estimated or approximate count of musicians involved with it.
- 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_69e77e82c9bc8190893090b2f6c64f1d |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b78f29481908cc8f390496dee97 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 21, 2026, 8:46 p.m.