Triple
T36116026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Juho Hänninen |
E1044615
|
entity |
| Predicate | hasDrivingLicenceType |
P19269
|
FINISHED |
| Object | FIA international competition licence |
—
|
NE NERFINISHED |
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: FIA international competition licence | Statement: [Juho Hänninen, hasDrivingLicenceType, FIA international competition licence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDrivingLicenceType Context triple: [Juho Hänninen, hasDrivingLicenceType, FIA international competition licence]
-
A.
typeOfLicense
chosen
Indicates the specific kind or category of license associated with an entity.
-
B.
hasDriverCategory
Indicates that an entity (such as a vehicle or driving role) is associated with a specific driver category or license class.
-
C.
hasLicense
Indicates that an entity possesses a valid authorization or permit, typically granted by an authority, to perform a specific activity or use something.
-
D.
canDrive
Indicates that one entity has the ability or permission to operate a vehicle or drive another entity.
-
E.
hasDrivingSkill
Indicates that an entity possesses the ability or competence to operate and control a vehicle.
- 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_69f76e344a4c8190af3858c6d78ba88f |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c29e1b848190b945c6c6120a5330 |
completed | May 3, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b6e7a881908deb96bedb2713f4 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:08 p.m.