Triple
T31674417
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MLS Rookie of the Year Award |
E808358
|
entity |
| Predicate | votingGroups |
P3462
|
FINISHED |
| Object | media |
—
|
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: media | Statement: [MLS Rookie of the Year Award, votingGroups, media]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: votingGroups Context triple: [MLS Rookie of the Year Award, votingGroups, media]
-
A.
votingUnit
chosen
Indicates a relationship where an entity functions as a unit or body that casts votes or participates in a voting process.
-
B.
votingScope
Indicates the range or domain within which a voting action or decision is valid, applicable, or authorized.
-
C.
votingControl
Indicates that one entity has the power to determine or significantly influence the outcome of decisions made by another entity through its voting rights.
-
D.
votingRegion
Indicates the geographic or administrative area in which an entity is eligible or authorized to vote.
-
E.
votingStatus
Indicates whether an entity is currently eligible, registered, or has participated in a voting process.
- 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_69f348dcf5d48190ac25b1365ae717a8 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6abaa1f648190b77073771df3bf3b |
completed | May 3, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1e84b88190b025f6ca40f17a8a |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 30, 2026, 11:02 p.m.