Triple
T3071143
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MLB All-Star Week |
E64023
|
entity |
| Predicate | fanParticipation |
P11584
|
FINISHED |
| Object | All-Star Game 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: All-Star Game voting | Statement: [MLB All-Star Week, fanParticipation, All-Star Game voting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fanParticipation Context triple: [MLB All-Star Week, fanParticipation, All-Star Game voting]
-
A.
participation
Indicates that an entity takes part in, contributes to, or is involved in a shared activity, event, or process with others.
-
B.
participationModel
chosen
Indicates how entities are involved in or contribute to an activity, process, or interaction.
-
C.
numberOfParticipants
Indicates the total count of entities involved in a particular event, activity, or relationship.
-
D.
fanAttendance
Indicates the number or presence of fans attending an event, such as a game, show, or performance.
-
E.
fanAccess
Indicates that an entity has permission or the ability to access fan-related content, features, or areas associated with another entity.
- 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_69ad857a8aec8190bfdfd9c14554ac5a |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada14b366881908e2ca104e5f38251 |
completed | March 8, 2026, 4:18 p.m. |
| PD | Predicate disambiguation | batch_69ad9625b30c819099ef9349c91d7b25 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3:02 p.m.