Triple
T15883190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Western Conference All-Stars |
E385124
|
entity |
| Predicate | captainSelection |
P31053
|
FINISHED |
| Object | top fan vote-getter in conference |
—
|
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: top fan vote-getter in conference | Statement: [Western Conference All-Stars, captainSelection, top fan vote-getter in conference]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: captainSelection Context triple: [Western Conference All-Stars, captainSelection, top fan vote-getter in conference]
-
A.
captainSelectionBasis
chosen
Indicates the criteria or basis on which an individual is chosen or designated to serve as captain.
-
B.
teamSelection
Indicates the assignment or choice of one or more individuals or entities to be part of a specific team.
-
C.
squadSelectionBasis
Indicates the criterion or rationale used to choose which individuals are included in a particular squad or team.
-
D.
captainPosition
Indicates that an entity holds the role or position of captain in relation to another entity (such as a team, vessel, or group).
-
E.
teamCaptain
Indicates that one entity serves as the captain or designated leader of a particular team.
- 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_69d86da4e86481909f1325fdc971b5ec |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e174de2cd48190ab18e48c9f051a2a |
completed | April 16, 2026, 11:46 p.m. |
| PD | Predicate disambiguation | batch_69e142c3e18c8190bb7b023f4a0eaebb |
completed | April 16, 2026, 8:12 p.m. |
Created at: April 10, 2026, 4:51 a.m.