Triple
T13674701
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sammy Angott |
E327842
|
entity |
| Predicate | notableWinType |
P111111
|
FINISHED |
| Object | points decision |
—
|
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: points decision | Statement: [Sammy Angott, notableWinType, points decision]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableWinType Context triple: [Sammy Angott, notableWinType, points decision]
-
A.
notableWin
Indicates that one entity achieved a particularly significant or distinguished victory over another or in a specific event.
-
B.
notableWinner
Indicates that the subject is a particularly distinguished or prominent winner of the referenced competition, award, or contest.
-
C.
notableOutcome
Indicates that an action, event, or entity leads to or is associated with a significant, noteworthy result or consequence.
-
D.
notableWinnerFeature
Indicates that a winner is distinguished by a particular notable characteristic or attribute.
-
E.
notablePlayerAchievement
Indicates that a player has accomplished a particularly significant or distinguished achievement within their activity or domain.
- 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_69d8076f1fa8819094664a59b55010df |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc65c04988190b675e6fb7241e53c |
completed | April 12, 2026, 4:20 p.m. |
| PD | Predicate disambiguation | batch_69dbbe8d8d0881908d6e89954f44eed4 |
completed | April 12, 2026, 3:47 p.m. |
| PDg | Predicate description generation | batch_69dbc59ca1a88190a6abd3bd00554c93 |
completed | April 12, 2026, 4:17 p.m. |
Created at: April 9, 2026, 9:53 p.m.