Triple
T21764655
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wario Land |
E537245
|
entity |
| Predicate | playerGoal |
P145862
|
FINISHED |
| Object | reach level exit |
—
|
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: reach level exit | Statement: [Wario Land, playerGoal, reach level exit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playerGoal Context triple: [Wario Land, playerGoal, reach level exit]
-
A.
goalScorer
Indicates that the subject is the player who scored a particular goal in a game or match.
-
B.
numberOfGoals
Indicates the total count of goals scored or achieved by an entity in a given context.
-
C.
isProlificGoalScorer
Indicates that an entity consistently scores a high number of goals, marking them as notably productive or effective in goal scoring.
-
D.
ownGoalBy
Indicates that a goal was accidentally scored against a team by the specified player (i.e., the player scored an own goal).
-
E.
topGoalScorerGoals
Indicates the number of goals scored by the top goal scorer in a given context or competition.
- 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_69e0c46f5d1c8190bf830409e98464e5 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f031a8a7f08190a4e50ebc24219585 |
completed | April 28, 2026, 4:03 a.m. |
| PD | Predicate disambiguation | batch_69e6be6299988190a34c98fa76d94700 |
completed | April 21, 2026, 12:01 a.m. |
| PDg | Predicate description generation | batch_69e6d054737081908aa7112975b77475 |
completed | April 21, 2026, 1:18 a.m. |
Created at: April 16, 2026, 6:51 p.m.