Triple
T21921546
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hans Moleman |
E541327
|
entity |
| Predicate | drivingRecord |
P146568
|
FINISHED |
| Object | frequently crashes vehicles |
—
|
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: frequently crashes vehicles | Statement: [Hans Moleman, drivingRecord, frequently crashes vehicles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: drivingRecord Context triple: [Hans Moleman, drivingRecord, frequently crashes vehicles]
-
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.
canDrive
Indicates that one entity has the ability or permission to operate a vehicle or drive another entity.
-
C.
hasDrivingSkill
Indicates that an entity possesses the ability or competence to operate and control a vehicle.
-
D.
drivesOn
Indicates that an entity uses or travels along a particular route, surface, or roadway as its path of movement.
-
E.
drivingPrinciple
Indicates that one entity functions as the core motivating idea, value, or rule that fundamentally guides or directs another entity’s behavior, decisions, or development.
- 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_69e0c47d74488190a15119108794a307 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f1233c29008190b84ae551b14eb2db |
completed | April 28, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69e6f5efc208819091ed2cf6841fa600 |
completed | April 21, 2026, 3:58 a.m. |
| PDg | Predicate description generation | batch_69e6fb6991948190a428c3c3bfd1c3b8 |
completed | April 21, 2026, 4:22 a.m. |
Created at: April 16, 2026, 7:45 p.m.