Triple
T29106861
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Weiqi |
E736783
|
entity |
| Predicate | notableAIEvent |
P203925
|
FINISHED |
| Object | AlphaGo defeating Lee Sedol in 2016 |
—
|
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: AlphaGo defeating Lee Sedol in 2016 | Statement: [Weiqi, notableAIEvent, AlphaGo defeating Lee Sedol in 2016]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableAIEvent Context triple: [Weiqi, notableAIEvent, AlphaGo defeating Lee Sedol in 2016]
-
A.
notableEventResponse
Indicates a response, reaction, or consequence that occurs as a result of a notable event.
-
B.
notableEventMentionedIn
Indicates that a particular notable event is referenced or discussed within a specified source or document.
-
C.
notableInternationalEvents
Indicates that the subject is associated with significant events that have international relevance or impact.
-
D.
notableEventPromoted
Indicates that an event was actively publicized, advertised, or otherwise promoted as notable or significant.
-
E.
notableEventIncluded
Indicates that a particular notable event is contained within, or forms part of, a larger collection, record, or context.
- F. None of above. chosen
Provenance (4 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_69f077ec765c81909474c88bcc8bab43 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_6a02f441bd408190923b6b68adee8fde |
completed | May 12, 2026, 9:34 a.m. |
| PD | Predicate disambiguation | batch_6a02f3c1e64881908569423c9f298f26 |
completed | May 12, 2026, 9:32 a.m. |
| PDg | Predicate description generation | batch_6a02f440f0e881909d669541aded3ca7 |
completed | May 12, 2026, 9:34 a.m. |
Created at: April 28, 2026, 11:16 a.m.