Triple
T20474225
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lester Leaps In |
E502268
|
entity |
| Predicate | originalEnsembleSize |
P83535
|
FINISHED |
| Object | small group |
—
|
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 group | Statement: [Lester Leaps In, originalEnsembleSize, small group]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalEnsembleSize Context triple: [Lester Leaps In, originalEnsembleSize, small group]
-
A.
intendedEnsembleSize
Indicates the number of participants or elements that a group, collection, or ensemble is designed or planned to contain.
-
B.
ensembleSize
chosen
Indicates the number of individual members or participants that make up a given group or ensemble.
-
C.
hasEnsembleNumbers
Indicates that an entity is associated with one or more ensemble numbers used to identify it within a grouped or collective context.
-
D.
typeOfEnsemble
Indicates the specific kind or category of ensemble that an entity belongs to or represents.
-
E.
mainEnsemble
Indicates that an entity serves as the primary or central ensemble associated with another entity (such as a work, performance, or production).
- 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_69e0b4ae5f1081908768b0c9a3a0bf38 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e699639eec81908f8bd24877b2b876 |
completed | April 20, 2026, 9:23 p.m. |
| PD | Predicate disambiguation | batch_69e57679eb40819086142df3e39c928e |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:33 a.m.