Triple
T36549235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PC Gamer MMO of the Year 2007 |
E901213
|
entity |
| Predicate | platformRecognized |
P96152
|
FINISHED |
| Object | PC |
—
|
NE NERFINISHED |
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: PC | Statement: [PC Gamer MMO of the Year 2007, platformRecognized, PC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: platformRecognized Context triple: [PC Gamer MMO of the Year 2007, platformRecognized, PC]
-
A.
recognizedPlatform
chosen
Indicates that one entity is acknowledged or accepted as an official or valid platform by another entity or authority.
-
B.
platformUsed
Indicates that an action, event, or interaction was carried out using a particular platform (e.g., software, service, or system) as the medium or tool.
-
C.
platformUsedFor
Indicates that one entity serves as the platform, medium, or environment utilized to perform, host, or support the activities of another entity.
-
D.
platformAppearsOn
Indicates that a particular platform is present, visible, or available within or on another specified context, medium, or environment.
-
E.
platformAdopted
Indicates that an entity has begun using or officially implemented a particular platform.
- 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_69f76e61217081908b79d610fe67b013 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c477a4d481908f52e55b6688f60c |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 3, 2026, 4:11 p.m.