Triple
T28897449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shang Tsung |
E732866
|
entity |
| Predicate | roleInFirstGame |
P100032
|
FINISHED |
| Object | final boss |
—
|
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: final boss | Statement: [Shang Tsung, roleInFirstGame, final boss]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInFirstGame Context triple: [Shang Tsung, roleInFirstGame, final boss]
-
A.
firstGamePlayed
Indicates the specific game that an entity participated in before any other, marking the earliest game in which it played.
-
B.
previouslyPlayedAs
Indicates that an entity had a former identity, role, or name under which it was known or operated in the past.
-
C.
associatedPlayerRole
Indicates a relationship where a specific role or function is linked to, or held by, a particular player.
-
D.
roleInGameplay
chosen
Indicates the specific function or responsibility an entity has within the context of gameplay or game mechanics.
-
E.
firstGameLoser
Indicates that the referenced entity is the one who lost the first game in a series, match, or competition.
- 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_69f05b08c2008190ac426a035a2ed66d |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69fea1f5d8c481908dc3351dc9ecef7f |
completed | May 9, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69fea06b6fe0819095bf4c1bc9809927 |
completed | May 9, 2026, 2:48 a.m. |
Created at: April 28, 2026, 8 a.m.