Triple
T37514835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grinding Gear Games |
E932608
|
entity |
| Predicate | platformSupportForPathOfExile |
P186793
|
FINISHED |
| Object | PC |
—
|
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: PC | Statement: [Grinding Gear Games, platformSupportForPathOfExile, PC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: platformSupportForPathOfExile Context triple: [Grinding Gear Games, platformSupportForPathOfExile, PC]
-
A.
platformRequirement
Indicates that one entity specifies a necessary platform or environment condition that must be met for another entity to function or be applicable.
-
B.
platformAppearsOn
Indicates that a particular platform is present, visible, or available within or on another specified context, medium, or environment.
-
C.
platformAvailabilityOfWork
chosen
Indicates that a particular work is available or accessible on a specified platform.
-
D.
platformTypeWorkedOn
Indicates the type of platform on which an entity (typically a person or system) has performed work or carried out activities.
-
E.
platformEligibility
Indicates whether an entity meets the required conditions to participate in or be used on a given 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_69f76ec730988190b5aa4f9cb9afd518 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd13595c81908719f52c3d37a7e8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:17 p.m.