Triple
T37471110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fracture Chambers |
E931153
|
entity |
| Predicate | isEndgameContentFor |
P100073
|
FINISHED |
| Object | level 60 characters in Shadowlands |
—
|
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: level 60 characters in Shadowlands | Statement: [Fracture Chambers, isEndgameContentFor, level 60 characters in Shadowlands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isEndgameContentFor Context triple: [Fracture Chambers, isEndgameContentFor, level 60 characters in Shadowlands]
-
A.
endgameContentFor
chosen
Indicates that something serves as endgame content designed for a particular game, mode, or player progression stage.
-
B.
hasGameContent
Indicates that an entity includes, provides, or is associated with game-related material or features.
-
C.
hasGameEndCondition
Indicates that an entity specifies the condition or set of conditions under which a game is considered finished or concluded.
-
D.
isFinalPlayBy
Indicates that a particular play or move is the last one performed by a specified entity in a sequence or event.
-
E.
playableInGame
Indicates that something can be used or controlled as an active element within a particular game.
- 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_69f76ec2af148190897d101070d7f415 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb8e61d5a48190afc273af1fb54af9 |
completed | May 6, 2026, 6:54 p.m. |
| PD | Predicate disambiguation | batch_69fb8d0c53c08190b64291bac58cdb4c |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:17 p.m.