Triple
T13119539
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Super Leaf |
E311685
|
entity |
| Predicate | has2DGameAppearances |
P108142
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Super Leaf, has2DGameAppearances, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: has2DGameAppearances Context triple: [Super Leaf, has2DGameAppearances, yes]
-
A.
hasGamesAt
Indicates that a particular location, venue, or platform hosts or offers one or more games.
-
B.
homeGamesPlayedBy
Indicates the number or set of home games that are played by a particular team or player.
-
C.
hasPlacementGames
Indicates that an entity is associated with one or more preliminary or qualifying games used to determine its ranking, tier, or initial placement.
-
D.
homeGamesPlayedIn
Indicates the venue or location where a team’s home games are played.
-
E.
homeGamesPlayedOn
Indicates that the specified home team plays its home games on the given date, day, or at the specified venue.
- 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_69d806a9fe888190b081e2d9ea665d6c |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98196e69081909111407ee3d9f08e |
completed | April 10, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69d98043a74c81908648e6cd0b4c7f71 |
completed | April 10, 2026, 10:57 p.m. |
| PDg | Predicate description generation | batch_69d98134df64819084a5674f9475dcc2 |
completed | April 10, 2026, 11:01 p.m. |
Created at: April 9, 2026, 9:06 p.m.