Triple
T15535569
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tilt-a-Kart |
E370330
|
entity |
| Predicate | platformFeature |
P118536
|
FINISHED |
| Object | tilting platform |
—
|
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: tilting platform | Statement: [Tilt-a-Kart, platformFeature, tilting platform]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: platformFeature Context triple: [Tilt-a-Kart, platformFeature, tilting platform]
-
A.
platformIncludes
Indicates that a platform contains, supports, or provides access to the specified component, feature, or content.
-
B.
targetPlatformFeature
chosen
Indicates that a particular feature is available on, or specifically associated with, a given target platform.
-
C.
platformRequirement
Indicates that one entity specifies a necessary platform or environment condition that must be met for another entity to function or be applicable.
-
D.
platformName
Indicates the name or identifier of the platform associated with the entity or action.
-
E.
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.
- 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_69d85cc521a08190921fb50319dddc34 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e0442e327c8190b4b879c8a3cd38e3 |
completed | April 16, 2026, 2:06 a.m. |
| PD | Predicate disambiguation | batch_69deda7a95c48190bbe29fadcf17191a |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:06 a.m.