Triple
T32510357
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tomb Raider fandom |
E830913
|
entity |
| Predicate | interactsOnPlatform |
P140410
|
FINISHED |
| Object |
—
|
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: Reddit | Statement: [Tomb Raider fandom, interactsOnPlatform, Reddit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: interactsOnPlatform Context triple: [Tomb Raider fandom, interactsOnPlatform, Reddit]
-
A.
focusesOnPlatform
Indicates that an entity’s attention, effort, or activity is primarily directed toward a particular platform as its main context or target.
-
B.
accessToPlatforms
Indicates that one entity is able to use, reach, or interact with certain platforms provided or controlled by another entity.
-
C.
relatedPlatformFunction
Indicates that one platform function is associated with, complements, or is otherwise functionally connected to another platform function.
-
D.
occursOnPlatform
chosen
Indicates that an event, action, or process takes place or is carried out on a specified platform.
-
E.
hasPlatformOn
Indicates that one entity is physically supported by or situated on the surface or structure of another 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_69f3492318348190ba37fb6b5f1d67f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd6f9d600c8190acf495b7fc632e4b |
completed | May 8, 2026, 5:07 a.m. |
| PD | Predicate disambiguation | batch_69fd6e98a2948190a9f78c415ad23b8c |
completed | May 8, 2026, 5:03 a.m. |
Created at: May 1, 2026, 1 a.m.