Triple
T15384607
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DK's Jungle Parkway |
E367885
|
entity |
| Predicate | offRoadBehavior |
P118553
|
FINISHED |
| Object | off-road areas cause rocks to be thrown at the player |
—
|
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: off-road areas cause rocks to be thrown at the player | Statement: [DK's Jungle Parkway, offRoadBehavior, off-road areas cause rocks to be thrown at the player]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offRoadBehavior Context triple: [DK's Jungle Parkway, offRoadBehavior, off-road areas cause rocks to be thrown at the player]
-
A.
terrainCapability
Indicates the types of terrain or ground conditions in which an entity can effectively operate or function.
-
B.
onRoad
Indicates that one entity is located on, traveling along, or otherwise situated upon a road.
-
C.
roadBuiltFor
Indicates that a road was constructed specifically to serve, provide access to, or support the use or needs of a particular entity.
-
D.
roadSide
Indicates that one entity is located along, beside, or immediately adjacent to a road.
-
E.
appliesToRoad
Indicates that something (such as a rule, condition, or attribute) is relevant or applicable specifically to a road.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69ded57005608190886cd01f640dfedb |
completed | April 15, 2026, 12:01 a.m. |
Created at: April 10, 2026, 3:19 a.m.