Triple
T35754223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Extreme E |
E1033396
|
entity |
| Predicate | hasNotableAmbassador |
P80170
|
FINISHED |
| Object | Lewis Hamilton |
E98401
|
NE 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: Lewis Hamilton | Statement: [Extreme E, hasNotableAmbassador, Lewis Hamilton]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableAmbassador Context triple: [Extreme E, hasNotableAmbassador, Lewis Hamilton]
-
A.
hasNotableSpeaker
Indicates that an event, gathering, or occasion features a speaker who is distinguished or noteworthy in some significant way.
-
B.
hasNotableMember
Indicates that a group, organization, or collection includes at least one member who is distinguished or noteworthy in some significant way.
-
C.
hasAmbassador
chosen
Indicates that one entity serves as an official diplomatic representative (ambassador) for another entity.
-
D.
hasNotablePromoter
Indicates that an entity is actively supported, publicized, or championed by a notable promoter.
-
E.
hasNotablePeople
Indicates that certain people associated with an entity are distinguished or noteworthy in some recognized way.
- F. None of above.
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_69f76e1262f48190a313318665acc189 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037ce70f54819082946dad8d380825 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3c170a56f08190b459c0cb792207f3 |
completed | June 24, 2026, 5:42 p.m. |
| PD | Predicate disambiguation | batch_6a037a069e6c8190857b611fffb7b867 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:06 p.m.