Triple
T27627555
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zappers |
E696248
|
entity |
| Predicate | rosterControl |
P162775
|
FINISHED |
| Object | fans influence roster moves |
—
|
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: fans influence roster moves | Statement: [Zappers, rosterControl, fans influence roster moves]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rosterControl Context triple: [Zappers, rosterControl, fans influence roster moves]
-
A.
rosterControl
chosen
Indicates a relationship where one entity manages, configures, or oversees the composition and changes of a group or roster of other entities.
-
B.
rosterBasis
Indicates the underlying criterion or rule used to determine which entities are included on a particular roster.
-
C.
rosterPurpose
Indicates the intended role, function, or use of a given roster within a particular context or system.
-
D.
rosterRequirement
Indicates that one entity specifies or imposes a required composition, number, or type of participants that must be included in another entity’s roster.
-
E.
rosterSize
Indicates the total number of individuals included on a given roster.
- 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_69ef59092c8881908114ad184248cc46 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f6359e3d3c81909814e2f0a7fb0ea9 |
completed | May 2, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f631871c888190bf29466fe4254e51 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 2:19 p.m.