Triple
T8482297
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lee Sedol |
E200548
|
entity |
| Predicate | famousMove |
P52554
|
FINISHED |
| Object | Move 78 in Game 4 vs AlphaGo |
—
|
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: Move 78 in Game 4 vs AlphaGo | Statement: [Lee Sedol, famousMove, Move 78 in Game 4 vs AlphaGo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: famousMove Context triple: [Lee Sedol, famousMove, Move 78 in Game 4 vs AlphaGo]
-
A.
madeFamousByFilm
Indicates that something became widely known or gained significant public recognition as a result of being featured in a film.
-
B.
famousRole
Indicates that an entity is best known for portraying or performing a particular role or character.
-
C.
mostFamouslyRecordedBy
Indicates that an item (such as a work, song, or performance) is best known or most widely associated with having been recorded by a particular entity.
-
D.
movementAlsoKnownAs
Indicates that a movement is referred to by an alternative name or alias.
-
E.
fameFor
chosen
Indicates that one entity is widely known or recognized specifically because of, or in connection with, 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_69ca831b17988190a1f3f3413d57b820 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe53638c48190b742fc51d1b4442a |
completed | March 31, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_69cbd104250c8190b4c499dcc9937494 |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:12 p.m.