Triple
T37961617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lilith |
E947020
|
entity |
| Predicate | roleInBorderlands3 |
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, roleInBorderlands3, playable character]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInBorderlands3 Context triple: [Lilith, roleInBorderlands3, playable character]
-
A.
roleInBorderlands
chosen
Indicates that an entity holds a specific role, function, or position within the context of the Borderlands setting or domain.
-
B.
roleInMassEffect3
Indicates that an entity has a specific role, appearance, or involvement in the video game *Mass Effect 3*.
-
C.
roleInGameplay
Indicates the specific function or responsibility an entity has within the context of gameplay or game mechanics.
-
D.
roleInOverwatch2
Indicates the specific function or position an entity holds within the context of Overwatch 2 (such as tank, damage, or support role).
-
E.
roleInPikmin3
Indicates the specific function, part, or involvement an entity has within the context of the game Pikmin 3.
- 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_6a0314e613f88190b5dbf89b9c4203c6 |
completed | May 12, 2026, 11:54 a.m. |
| PD | Predicate disambiguation | batch_6a0314699c1c8190b2a80dc4015e7890 |
completed | May 12, 2026, 11:52 a.m. |
Created at: May 3, 2026, 4:20 p.m.