Triple
T30315957
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apple Design Awards 2010 |
E771054
|
entity |
| Predicate | hostEventType |
P58154
|
FINISHED |
| Object | developer conference award program |
—
|
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: developer conference award program | Statement: [Apple Design Awards 2010, hostEventType, developer conference award program]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostEventType Context triple: [Apple Design Awards 2010, hostEventType, developer conference award program]
-
A.
hostsTypeOfEvent
chosen
Indicates that an entity organizes or provides the venue for a particular type or category of event.
-
B.
hostsEvent
Indicates that an entity organizes and provides the venue or setting for an event to take place.
-
C.
alsoHostedEventType
Indicates that the same host was responsible for organizing or holding another event of a specified type.
-
D.
hostVenueInstanceOf
Indicates that a specific host venue is an instance or concrete realization of a more general venue type or category.
-
E.
hostsVenue
Indicates that an entity provides or manages a location where an event or activity takes place.
- 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_69f22488f224819081b0f3ec41ab975c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6b903538481909cffcb6cc1cc0e70 |
completed | May 3, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69f6b626120c819097c9ad04487570d7 |
completed | May 3, 2026, 2:42 a.m. |
Created at: April 29, 2026, 7:51 p.m.