Triple
T30572278
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lawrence Stroll |
E778149
|
entity |
| Predicate | hasRoleInMotorsport |
P59905
|
FINISHED |
| Object | team owner |
—
|
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: team owner | Statement: [Lawrence Stroll, hasRoleInMotorsport, team owner]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoleInMotorsport Context triple: [Lawrence Stroll, hasRoleInMotorsport, team owner]
-
A.
motorsportHomologationRole
Indicates the specific role or function an entity has within the homologation (official approval and certification) process in motorsport.
-
B.
hasMotorsportInvolvement
Indicates that an entity is involved in motorsport, such as through participation, organization, sponsorship, or other direct association with motor racing activities.
-
C.
motorsportRole
chosen
Indicates the specific function or position an entity holds within the context of motorsport activities or events.
-
D.
hasRoleInRace
Indicates that an entity participates in a race with a specific role or function.
-
E.
roleAtIRacing
Indicates the specific role, position, or function an entity holds within the iRacing organization or platform.
- 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_69f2249f8c148190ae7eb3912cde112a |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fcf825ca7081909d06b0df33eb33f9 |
completed | May 7, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fcf42160f0819096812a8bf590875e |
completed | May 7, 2026, 8:20 p.m. |
Created at: April 29, 2026, 8:22 p.m.