Triple
T37509097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lords of Dread |
E932171
|
entity |
| Predicate | requiresPlayerRole |
P6843
|
FINISHED |
| Object | tank |
—
|
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: tank | Statement: [Lords of Dread, requiresPlayerRole, tank]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresPlayerRole Context triple: [Lords of Dread, requiresPlayerRole, tank]
-
A.
requiresPlayers
Indicates that one entity needs a certain number or set of players to participate, function, or be valid.
-
B.
requiresRole
chosen
Indicates that performing an action or accessing a resource is contingent on the subject having a specified role or set of roles.
-
C.
supportsRole
Indicates that one entity provides the necessary functionality, resources, or conditions for another entity to perform or occupy a specific role.
-
D.
requiresMember
Indicates that one entity depends on or mandates the participation, presence, or inclusion of another entity as a member in order for a condition, action, or relationship to hold.
-
E.
hasPlayingRole
Indicates that an entity participates in an activity, event, or performance in a specific playing role or capacity.
- 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_69f76ec5268481909ea01c73aeeefd42 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a00694f72888190983fee7d687a6daa |
completed | May 10, 2026, 11:17 a.m. |
| PD | Predicate disambiguation | batch_6a00685dbf44819098ea0c86bb9e50d8 |
completed | May 10, 2026, 11:13 a.m. |
Created at: May 3, 2026, 4:17 p.m.