Triple
T10116801
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PCH |
E223178
|
entity |
| Predicate | hasDrivingExperience |
P73396
|
FINISHED |
| Object | winding roads |
—
|
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: winding roads | Statement: [PCH, hasDrivingExperience, winding roads]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDrivingExperience Context triple: [PCH, hasDrivingExperience, winding roads]
-
A.
drivingExperience
Indicates the extent or history of a person's involvement in driving vehicles, typically measured by duration, frequency, or level of skill.
-
B.
hasDrivingSkill
Indicates that an entity possesses the ability or competence to operate and control a vehicle.
-
C.
hasDrivingConditions
chosen
Indicates that a particular route, area, or time period is associated with specific driving conditions (such as weather, traffic, or road surface state) that affect how vehicles can be driven.
-
D.
drivingExperienceBooking
Indicates that an entity books or reserves a driving experience activity for themselves or someone else.
-
E.
hasDriverCategory
Indicates that an entity (such as a vehicle or driving role) is associated with a specific driver category or license class.
- 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_69ca8422047c81909d66b717b8b18cf3 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cdd162fac0819084c74947c1f6688e |
completed | April 2, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69cd4b9ed7e48190aa132ef8a69b49f9 |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:04 p.m.