Triple
T15579311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Co-Star Mode |
E374450
|
entity |
| Predicate | primaryPlayerRole |
P39782
|
FINISHED |
| Object | core platforming |
—
|
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: core platforming | Statement: [Co-Star Mode, primaryPlayerRole, core platforming]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryPlayerRole Context triple: [Co-Star Mode, primaryPlayerRole, core platforming]
-
A.
associatedPlayerRole
chosen
Indicates a relationship where a specific role or function is linked to, or held by, a particular player.
-
B.
primaryPlayerSource
Indicates that an entity serves as the main origin or provider of a player within a given context or system.
-
C.
lineupRole
Indicates the specific role or position an entity holds within a lineup or ordered group.
-
D.
primaryActor
Indicates that the referenced entity is the main participant or most central party responsible for the action or event in the relationship.
-
E.
primaryUseByPlayers
Indicates the main way in which players typically use or interact with the referenced 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_69d85ccd575081908909b71a3f3e3a61 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04e24064c8190b132c3092877fbfa |
completed | April 16, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69deda817e9881909b0c66fc9056f7d5 |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:11 a.m.