Triple
T21419720
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SK |
E528402
|
entity |
| Predicate | hasDrivingCode |
P43433
|
FINISHED |
| Object | SK |
—
|
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: SK | Statement: [SK, hasDrivingCode, SK]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDrivingCode Context triple: [SK, hasDrivingCode, SK]
-
A.
drivingCode
chosen
Indicates that one entity is the driving or causal code responsible for initiating, controlling, or determining the behavior or outcome of another entity.
-
B.
hasDrivingConditions
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.
-
C.
hasDrivingStyle
Indicates the characteristic manner or pattern in which an entity typically drives.
-
D.
canDrive
Indicates that one entity has the ability or permission to operate a vehicle or drive another entity.
-
E.
hasRacingCode
Indicates that an entity is associated with a specific racing classification or identifier code.
- 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_69e0c454c248819093425d1099101c09 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e8b2cdb40481909542f2c953bbab64 |
completed | April 22, 2026, 11:36 a.m. |
| PD | Predicate disambiguation | batch_69e61633f8208190a2a849457c4e4198 |
completed | April 20, 2026, 12:04 p.m. |
Created at: April 16, 2026, 5:47 p.m.