Triple
T1112051
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NBA All-Star Game |
E11016
|
entity |
| Predicate | participantSelectionMethod |
P2726
|
FINISHED |
| Object | fan voting |
—
|
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: fan voting | Statement: [NBA All-Star Game, participantSelectionMethod, fan voting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: participantSelectionMethod Context triple: [NBA All-Star Game, participantSelectionMethod, fan voting]
-
A.
selectionProcess
Indicates the procedure or set of steps by which one or more options are evaluated and chosen from a larger set of candidates.
-
B.
votingMethod
chosen
Indicates the procedure or system by which a vote is cast, collected, and counted in a decision-making or electoral process.
-
C.
hasMemberSelectionMethod
Indicates the method or criteria by which members of a group, organization, or body are chosen or selected.
-
D.
electionMethod
Indicates the process or system used to select a candidate or make a decision in an election.
-
E.
selectionMethodUpperHouse
Indicates how members of the upper house are chosen or appointed (e.g., by election, appointment, or other selection procedures).
- 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_69a493252a648190ac48f8742474a5e8 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4bbd92a8c8190a16e55f3f739010f |
completed | March 1, 2026, 10:21 p.m. |
| PD | Predicate disambiguation | batch_69a4bb42990c819080db96478fd4977e |
completed | March 1, 2026, 10:18 p.m. |
Created at: March 1, 2026, 7:43 p.m.