Triple
T35752007
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Englebert |
E1033342
|
entity |
| Predicate | usedInMotorsportCategory |
P128813
|
FINISHED |
| Object | Formula One |
—
|
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: Formula One | Statement: [Englebert, usedInMotorsportCategory, Formula One]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInMotorsportCategory Context triple: [Englebert, usedInMotorsportCategory, Formula One]
-
A.
hasMotorsportInvolvement
Indicates that an entity is involved in motorsport, such as through participation, organization, sponsorship, or other direct association with motor racing activities.
-
B.
isMotorSportEventIn
Indicates that a particular motorsport event takes place within a specified location or venue.
-
C.
motorsportPurpose
Indicates that something exists or is used specifically for the purpose of participating in or supporting motorsport activities or events.
-
D.
motorsportRole
Indicates the specific function or position an entity holds within the context of motorsport activities or events.
-
E.
motorsportClass
chosen
Indicates that one entity is classified as a specific motorsport category or division associated with another entity.
- 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_69f76e1262f48190a313318665acc189 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fedfd913f48190bdcd450980868d9a |
completed | May 9, 2026, 7:18 a.m. |
| PD | Predicate disambiguation | batch_69fedf58c6e88190821a7156054c9086 |
completed | May 9, 2026, 7:16 a.m. |
Created at: May 3, 2026, 4:06 p.m.