Triple
T3778191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MyCareer mode |
E83357
|
entity |
| Predicate | playerControl |
P50877
|
FINISHED |
| Object | single custom-created player |
—
|
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: single custom-created player | Statement: [MyCareer mode, playerControl, single custom-created player]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playerControl Context triple: [MyCareer mode, playerControl, single custom-created player]
-
A.
mediaControl
Indicates a relationship where one entity directs, regulates, or influences the creation, distribution, or content of media controlled by another entity.
-
B.
playIn
Indicates that an entity participates or performs in a particular event, context, or location (such as a game, match, or venue).
-
C.
startOfMediaControl
Indicates the point in time or event at which a media control action (such as play, pause, or seek) is initiated.
-
D.
playingPosition
Indicates the specific role or position an individual occupies while participating in a game or sport.
-
E.
playType
Indicates the specific category or style of play or performance associated with an event or action.
- F. None of above. chosen
Provenance (4 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_69ad8b235e608190b5a2b1d1bfcef50b |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcc78173081908b230017834cdf9e |
completed | March 8, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_69adc050cc5c81909d9855f866f3c26d |
completed | March 8, 2026, 6:30 p.m. |
| PDg | Predicate description generation | batch_69adc0fe3e3c8190bd886c7745c172a0 |
completed | March 8, 2026, 6:33 p.m. |
Created at: March 8, 2026, 3:36 p.m.