Triple
T9500686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AlphaGo Zero |
E229130
|
entity |
| Predicate | achievedLevel |
P1518
|
FINISHED |
| Object | superhuman performance in Go |
—
|
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: superhuman performance in Go | Statement: [AlphaGo Zero, achievedLevel, superhuman performance in Go]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: achievedLevel Context triple: [AlphaGo Zero, achievedLevel, superhuman performance in Go]
-
A.
achievementLevel
Indicates the degree or extent to which an entity has attained a particular goal, standard, or performance outcome.
-
B.
achievementStatus
Indicates the current state or level of completion of an achievement-related goal or milestone for an entity.
-
C.
achieved
chosen
Indicates that an entity successfully reached, obtained, or accomplished a specified goal, result, or state.
-
D.
assessmentLevel
Indicates the degree, rating, or intensity assigned to an evaluation or judgment of something.
-
E.
hasAwardLevel
Indicates that an entity possesses or has been assigned a specific level, tier, or rank within an award or recognition system.
- 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_69ca84753660819098e8d416e89e26ae |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd983c308c8190bde6858ac1ca8ea5 |
completed | April 1, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69cca5651a588190a3cfebe249a223e5 |
completed | April 1, 2026, 4:56 a.m. |
Created at: March 30, 2026, 7:57 p.m.