Triple
T22850624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shumang Leela |
E566345
|
entity |
| Predicate | usesElaborateSets |
P149946
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [Shumang Leela, usesElaborateSets, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesElaborateSets Context triple: [Shumang Leela, usesElaborateSets, no]
-
A.
hasExpansionSetNumber
Indicates that an entity is associated with a specific numbered position or identifier within an expansion set.
-
B.
setsIn
Indicates that one entity places or positions another entity into or within a specified container, location, or context.
-
C.
hasBasicCardSet
Indicates that an entity is associated with or includes a fundamental or default set of cards.
-
D.
featuresSoloSets
Indicates that the subject includes or presents one or more solo performance sets as part of its content or structure.
-
E.
hasSestet
Indicates that something (typically a poem or sonnet) contains a sestet, i.e., a six-line stanza or final six-line section.
- F. None of above. chosen
Provenance (4 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_69e2458750b481908a8e4cf4609cc6cf |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17eb8b3588190b2bc8e7021f9ef10 |
completed | April 29, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69eed2d507c08190895ed971af0fc755 |
completed | April 27, 2026, 3:07 a.m. |
| PDg | Predicate description generation | batch_69eeeb577e2081909f4a4e9c296535c0 |
completed | April 27, 2026, 4:51 a.m. |
Created at: April 17, 2026, 3:36 p.m.