Triple
T22374278
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Misko Hevery |
E553114
|
entity |
| Predicate | speakerAt |
P10206
|
FINISHED |
| Object | software development conferences |
—
|
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: software development conferences | Statement: [Misko Hevery, speakerAt, software development conferences]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: speakerAt Context triple: [Misko Hevery, speakerAt, software development conferences]
-
A.
speakerMP
Indicates that the subject is a Member of Parliament who holds or is identified with the role of Speaker (or a speaker-related parliamentary position).
-
B.
spokeAt
chosen
Indicates that a person delivered a talk, speech, or presentation at a particular event or location.
-
C.
speakerInText
Indicates that a given entity is the person who speaks or is quoted within a particular text or textual segment.
-
D.
spokenOn
Indicates that an utterance or speech act occurred at or during a specific time or date.
-
E.
speakers
Indicates that one or more entities produce spoken language or vocal communication, typically addressing an audience or participating in a conversation.
- 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_69e11e4c03248190a26a5060ea6973ee |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15806b534819083716c2b090ede42 |
completed | April 29, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69e73011e6388190a05edf137f488441 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:45 p.m.