Triple
T33421823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Need for Speed II |
E855865
|
entity |
| Predicate | hasTrackEnvironment |
P115885
|
FINISHED |
| Object | canyons |
—
|
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: canyons | Statement: [Need for Speed II, hasTrackEnvironment, canyons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTrackEnvironment Context triple: [Need for Speed II, hasTrackEnvironment, canyons]
-
A.
hasTrackContext
Indicates that an entity is associated with or occurs within a particular track-related context (such as a specific track, route, or sequence).
-
B.
hasTrack
Indicates that one entity possesses, includes, or is associated with a specific track (such as a path, course, or recorded item).
-
C.
hasTrackControl
Indicates that one entity has authority or capability to manage, direct, or regulate the operation or behavior of another entity’s track or tracking process.
-
D.
hasTrackSurface
chosen
Indicates that an entity (such as a track) possesses or is characterized by a particular type of surface.
-
E.
hasTrackFeatures
Indicates that something possesses or is associated with specific track-related characteristics or attributes.
- 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_69f3496fdf0081908c1aa30870ce518b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff397e19a88190a945b826159f5290 |
completed | May 9, 2026, 1:41 p.m. |
| PD | Predicate disambiguation | batch_69ff392400d0819088d30d08d4a774bd |
completed | May 9, 2026, 1:39 p.m. |
Created at: May 1, 2026, 1:36 a.m.