Triple
T37961664
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mordecai |
E947021
|
entity |
| Predicate | nonPlayableIn |
P88329
|
FINISHED |
| Object | Borderlands 2 |
—
|
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: Borderlands 2 | Statement: [Mordecai, nonPlayableIn, Borderlands 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nonPlayableIn Context triple: [Mordecai, nonPlayableIn, Borderlands 2]
-
A.
notPlayableInMultiplayer
Indicates that the referenced content or action cannot be used or accessed in multiplayer mode.
-
B.
playableInGame
chosen
Indicates that something can be used or controlled as an active element within a particular game.
-
C.
notAvailableFor
Indicates that an entity is currently not accessible, usable, or eligible for a particular action, purpose, or association.
-
D.
playableInStandard
Indicates that a game element (such as a card or item) is legally usable within the rules of the Standard format of play.
-
E.
canAlsoBePlayedIn
Indicates that something (such as a game, media, or activity) is additionally playable or usable in another context, format, or environment beyond its primary one.
- 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_69f76ef7062c819091bfacb7e83aa1e0 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc7b78f9481909f4f8fc2e3fdcde1 |
completed | May 6, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69fbbd18c9908190928d274f8731dfa8 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:20 p.m.