Triple
T25255816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lifetime Achievement Award |
E633169
|
entity |
| Predicate | isOftenAnnouncedAt |
P430
|
FINISHED |
| Object | 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: conferences | Statement: [Lifetime Achievement Award, isOftenAnnouncedAt, conferences]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOftenAnnouncedAt Context triple: [Lifetime Achievement Award, isOftenAnnouncedAt, conferences]
-
A.
publiclyAnnouncedBy
Indicates that an action, decision, or piece of information was formally communicated to the public by a specified agent or entity.
-
B.
announcedTo
Indicates that one entity formally communicated or made known some information, decision, or event to another specific entity.
-
C.
announcedFor
Indicates that one entity has been publicly declared or made known in connection with, or on behalf of, another entity.
-
D.
announcedThrough
Indicates that an announcement or communication was made via a particular medium, channel, or intermediary.
-
E.
announcedAt
chosen
Indicates that an announcement or declaration was made at a specific time or event.
- 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_69e75a922ad481908f4f1f884583cb42 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f5f6baf2d48190a6a4cd6501be87d2 |
completed | May 2, 2026, 1:06 p.m. |
| PD | Predicate disambiguation | batch_69f5afd5baac8190bb8ed576813c8591 |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 21, 2026, 1:13 p.m.