Triple
T27464381
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arnage corner |
E693135
|
entity |
| Predicate | drivingSkillRequired |
P29486
|
FINISHED |
| Object | precise braking |
—
|
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: precise braking | Statement: [Arnage corner, drivingSkillRequired, precise braking]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: drivingSkillRequired Context triple: [Arnage corner, drivingSkillRequired, precise braking]
-
A.
hasDrivingSkill
Indicates that an entity possesses the ability or competence to operate and control a vehicle.
-
B.
driverRequirement
chosen
Indicates that a certain driver, qualification, or driving-related condition is required for an entity to perform or be associated with a particular role, task, or operation.
-
C.
drivingDiscipline
Indicates the manner and quality of how an entity operates a vehicle, especially in terms of adherence to traffic rules and safe driving behavior.
-
D.
canDrive
Indicates that one entity has the ability or permission to operate a vehicle or drive another entity.
-
E.
drivingExperience
Indicates the extent or history of a person's involvement in driving vehicles, typically measured by duration, frequency, or level of skill.
- 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_69ef538105548190a771cc5a0cf8c211 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69f6359e3d3c81909814e2f0a7fb0ea9 |
completed | May 2, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f631871c888190bf29466fe4254e51 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 12:51 p.m.