Triple
T36284537
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ulf Andersson |
E893036
|
entity |
| Predicate | notableGameCharacteristics |
P122493
|
FINISHED |
| Object | high drawing percentage |
—
|
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: high drawing percentage | Statement: [Ulf Andersson, notableGameCharacteristics, high drawing percentage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableGameCharacteristics Context triple: [Ulf Andersson, notableGameCharacteristics, high drawing percentage]
-
A.
notableTraitInGames
chosen
Indicates that a particular characteristic or quality is especially prominent or well-known in the context of games.
-
B.
notableGameFeature
Indicates that a particular game feature is especially significant, distinctive, or noteworthy in the context of the game.
-
C.
notableLeagueCharacteristic
Indicates that a particular characteristic is especially prominent or defining for a given league.
-
D.
notableGame
Indicates that a particular game is especially significant, prominent, or well-known in relation to the associated entity.
-
E.
notableFeat
Indicates that an entity is recognized for having achieved or performed a particularly significant or distinguished feat.
- 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_69f76e4955c08190b8cfddca34fc0242 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0a54cc8190868c1bfa1590d1a6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:09 p.m.