Triple
T37458242
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wild |
E930852
|
entity |
| Predicate | hasLeaderboard |
P2583
|
FINISHED |
| Object | Wild Legend ladder |
—
|
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: Wild Legend ladder | Statement: [Wild, hasLeaderboard, Wild Legend ladder]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLeaderboard Context triple: [Wild, hasLeaderboard, Wild Legend ladder]
-
A.
hasScoreboard
chosen
Indicates that one entity is equipped with or associated with a scoreboard used to display scores or results.
-
B.
hasScoreboardLocation
Indicates the spatial or logical position where a scoreboard is placed or associated within a given context.
-
C.
pointsLeader
Indicates that the subject entity is the current leader in points relative to other entities in a given context or competition.
-
D.
leagueLeader
Indicates that the subject entity is currently ranked first or holds the top position within a specified league or competitive grouping.
-
E.
hasScoreAvailable
Indicates that a score or rating for the relevant entity is present and can be accessed.
- 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fe86cad5108190b0164b8bc6fc23ea |
completed | May 9, 2026, 12:58 a.m. |
| PD | Predicate disambiguation | batch_69fe83c0c9888190b6fc40c7f727b569 |
completed | May 9, 2026, 12:45 a.m. |
Created at: May 3, 2026, 4:17 p.m.