Triple
T15384361
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frappe Snowland |
E367880
|
entity |
| Predicate | obstacleEffect |
P111256
|
FINISHED |
| Object | causes spin-outs on collision |
—
|
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: causes spin-outs on collision | Statement: [Frappe Snowland, obstacleEffect, causes spin-outs on collision]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: obstacleEffect Context triple: [Frappe Snowland, obstacleEffect, causes spin-outs on collision]
-
A.
obstacles
Indicates that one entity presents barriers, hindrances, or impediments that block or restrict another entity’s progress, action, or interaction.
-
B.
obstacleHeightCharacteristic
Indicates the characteristic or measured value of an obstacle’s height in relation to a reference level or path.
-
C.
movementEffect
chosen
Indicates how one entity’s movement causes a change or effect in another entity or in the environment.
-
D.
hasDifficultyEffect
Indicates that one entity causes a change in the difficulty level or challenge associated with another entity or activity.
-
E.
gravityAffected
Indicates that an entity is subject to the force of gravity, causing it to accelerate or move in response to gravitational pull.
- 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_69d85a1551a08190ba2caea7cd51c639 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e7397188190bde42b897ab4b5b4 |
completed | April 16, 2026, 1:42 a.m. |
| PD | Predicate disambiguation | batch_69ded27742a881909cd73cc5c7d062fd |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:19 a.m.