Triple
T22106189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bill Palmer |
E546291
|
entity |
| Predicate | hasPresentedAt |
P36704
|
FINISHED |
| Object | linguistics 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: linguistics conferences | Statement: [Bill Palmer, hasPresentedAt, linguistics conferences]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPresentedAt Context triple: [Bill Palmer, hasPresentedAt, linguistics conferences]
-
A.
hasPresented
Indicates that one entity has formally given, delivered, or shown something (such as information, a work, or an award) to another entity.
-
B.
presentsAt
chosen
Indicates that one entity delivers or gives a presentation, talk, or performance at a particular event, venue, or occasion.
-
C.
hasPresentation
Indicates that an entity delivers, contains, or is associated with a specific presentation (such as a talk, slide deck, or formal display of information).
-
D.
hasExhibitedAt
Indicates that an entity has displayed or presented its work at a particular event, venue, or exhibition.
-
E.
presentedAfter
Indicates that one entity is presented or displayed at a later time or sequence position than 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_69e11e378dc08190896d6a51597afd5a |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f12919dd388190b8ca08e2464cb0b8 |
completed | April 28, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69e71b2ed7348190b6fa2e52f54393fb |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:30 p.m.