Triple
T37665915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cascade Kingdom |
E937818
|
entity |
| Predicate | followsInGame |
P200275
|
FINISHED |
| Object | Cap Kingdom |
—
|
NE NERFINISHED |
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: Cap Kingdom | Statement: [Cascade Kingdom, followsInGame, Cap Kingdom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsInGame Context triple: [Cascade Kingdom, followsInGame, Cap Kingdom]
-
A.
playsInGame
Indicates that an entity participates as a player in a particular game or match.
-
B.
performedInGame
Indicates that an action or event was carried out during a particular game or match.
-
C.
playableInGame
Indicates that something can be used or controlled as an active element within a particular game.
-
D.
inGameBehavior
Indicates how an entity acts, responds, or conducts itself within the context of a game or gameplay scenario.
-
E.
playInGameIntroduced
Indicates that an entity participates as a playable element within the specific game in which it was first introduced.
- 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff7dcedab08190a719a707d03306e2 |
completed | May 9, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69ff7d0119348190ad462554e81190fe |
completed | May 9, 2026, 6:29 p.m. |
| PDg | Predicate description generation | batch_69ff7dce25d88190b167a014661bc4ba |
completed | May 9, 2026, 6:32 p.m. |
Created at: May 3, 2026, 4:18 p.m.