Triple
T1365780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Martin Eberhard |
E29998
|
entity |
| Predicate | hasGivenPresentationOn |
P10206
|
FINISHED |
| Object | electric vehicle technology |
—
|
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: electric vehicle technology | Statement: [Martin Eberhard, hasGivenPresentationOn, electric vehicle technology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGivenPresentationOn Context triple: [Martin Eberhard, hasGivenPresentationOn, electric vehicle technology]
-
A.
succeededAsSpeakerBy
Indicates that one entity took over the role or position of speaker from another entity as their successor.
-
B.
spokeAt
chosen
Indicates that a person delivered a talk, speech, or presentation at a particular event or location.
-
C.
hasSpeakersIn
Indicates that an entity (such as an event, conference, or session) includes or is associated with speakers located in or belonging to a specified place or group.
-
D.
hasPublication
Indicates that an entity is associated with or responsible for a specific publication.
-
E.
presentedFor
Indicates that one entity was formally offered, submitted, or shown to another entity for consideration, review, or action.
- 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_69a498f912008190a376a98b207b2071 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c2d1d15481909d58b6fd8aa2e585 |
completed | March 1, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69a4bef945c08190a027472fdd695ea5 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:57 p.m.