Triple
T38590086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elementium Reinforced Bulwark |
E932433
|
entity |
| Predicate | usableByRole |
P28456
|
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: [Elementium Reinforced Bulwark, usableByRole, tank]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usableByRole Context triple: [Elementium Reinforced Bulwark, usableByRole, tank]
-
A.
usesRoleTypes
Indicates that an entity employs or is associated with specific role classifications or role types within a given context.
-
B.
usableAs
Indicates that one entity can function in place of or serve the purpose of another entity.
-
C.
effectiveRole
Indicates the functional role or capacity an entity actually performs or holds in a given context, regardless of its formal or nominal designation.
-
D.
canBeUsed
Indicates that one entity is suitable or available to serve a particular function, purpose, or role in relation to another entity or context.
-
E.
possibleRole
chosen
Indicates that an entity is capable of or eligible to serve in a particular role or function in a given context.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdfbc71c481908ba7f87907b17782 |
completed | May 7, 2026, 6:53 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe580b8819087f143596b2c79c0 |
completed | May 7, 2026, 6:37 p.m. |
Created at: May 3, 2026, 4:32 p.m.