Triple
T31885229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Championships (tenpin bowling) |
E813989
|
entity |
| Predicate | laneCondition |
P172695
|
FINISHED |
| Object | sport oil patterns |
—
|
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: sport oil patterns | Statement: [World Championships (tenpin bowling), laneCondition, sport oil patterns]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laneCondition Context triple: [World Championships (tenpin bowling), laneCondition, sport oil patterns]
-
A.
hasRoadCondition
Indicates that a specified road segment possesses or is characterized by a particular condition or state (e.g., quality, surface, or status).
-
B.
roadEnvironment
Indicates that the relationship or action occurs within, is influenced by, or is specifically associated with a road or roadway environment.
-
C.
laneSurface
Indicates the type or condition of the surface that makes up a lane used for travel or traffic.
-
D.
laneRequirement
Indicates that a specified number or type of lanes is required for a particular movement, maneuver, or use on a roadway.
-
E.
onRoad
Indicates that one entity is located on, traveling along, or otherwise situated upon 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_69f348ed74bc81909846aaa6a3c7318c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6b0daa4988190b78498e7da6a30dd |
completed | May 3, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69f6aca59d4881908d14ed47962703bd |
completed | May 3, 2026, 2:02 a.m. |
| PDg | Predicate description generation | batch_69f6af7d92008190aead47eaae8cc091 |
completed | May 3, 2026, 2:14 a.m. |
Created at: April 30, 2026, 11:57 p.m.