Triple
T7421102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coons Award |
E171246
|
entity |
| Predicate | typicalPresentationVenue |
P25526
|
FINISHED |
| Object | annual SIGGRAPH conference |
—
|
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: annual SIGGRAPH conference | Statement: [Coons Award, typicalPresentationVenue, annual SIGGRAPH conference]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalPresentationVenue Context triple: [Coons Award, typicalPresentationVenue, annual SIGGRAPH conference]
-
A.
typicalVenues
chosen
Indicates that the specified locations are common or standard places where the associated activity, event, or entity usually occurs or is hosted.
-
B.
venue
Indicates the place or location where an event, activity, or interaction takes place.
-
C.
presentsAt
Indicates that one entity delivers or gives a presentation, talk, or performance at a particular event, venue, or occasion.
-
D.
intendedPerformanceVenue
Indicates the venue or location where a performance is planned or intended to take place.
-
E.
usualVenueSince
Indicates that a particular venue has been the regular or customary location for something (e.g., an event or activity) starting from a specified point in time.
- 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_69c68a625d048190af70eb8b63bec5a0 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f2ebc520819087cfc2eb9dda0e17 |
completed | March 27, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69c6f0345040819094c5756dfa487faf |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:11 p.m.