Triple
T37961613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lilith |
E947020
|
entity |
| Predicate | roleInBorderlands |
P204050
|
FINISHED |
| Object | playable character |
—
|
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: playable character | Statement: [Lilith, roleInBorderlands, playable character]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInBorderlands Context triple: [Lilith, roleInBorderlands, playable character]
-
A.
roleInGameplay
Indicates the specific function or responsibility an entity has within the context of gameplay or game mechanics.
-
B.
roleInOverwatch2
Indicates the specific function or position an entity holds within the context of Overwatch 2 (such as tank, damage, or support role).
-
C.
roleInFrontier
Indicates that an entity holds a specific role or position within the context of a frontier (such as a boundary, pioneering area, or cutting-edge domain).
-
D.
roleInD2
Indicates that an entity holds a specific role or function within a D2-related context, structure, or process.
-
E.
roleAtBungie
Indicates that an entity holds or held a specific role or position at the organization Bungie.
- 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_69f76ef7062c819091bfacb7e83aa1e0 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a0311c202408190be88a85337aacf11 |
completed | May 12, 2026, 11:40 a.m. |
| PD | Predicate disambiguation | batch_6a0310b0c9c88190ab218d47d4f432ed |
completed | May 12, 2026, 11:36 a.m. |
| PDg | Predicate description generation | batch_6a0311c145a08190ba7658db898ab7d6 |
completed | May 12, 2026, 11:40 a.m. |
Created at: May 3, 2026, 4:20 p.m.