Triple
T15537163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Green Shell |
E370376
|
entity |
| Predicate | canRicochetOff |
P119086
|
FINISHED |
| Object | walls |
—
|
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: walls | Statement: [Green Shell, canRicochetOff, walls]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canRicochetOff Context triple: [Green Shell, canRicochetOff, walls]
-
A.
canBeDodgedBy
Indicates that an action, effect, or attack is avoidable by a particular entity through dodging.
-
B.
canReach
Indicates that one entity is able to access, arrive at, or establish a path to another entity.
-
C.
attackFeasibility
Indicates the extent to which carrying out an attack is practically possible given current conditions, capabilities, and constraints.
-
D.
canBring
Indicates that one entity has the ability or permission to bring another entity or item to a particular place or context.
-
E.
canBe
Indicates that one entity has the potential, permission, or capability to become, perform as, or be classified as another entity.
- 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_69d85cc521a08190921fb50319dddc34 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e0442f3c688190a599165e526af2ed |
completed | April 16, 2026, 2:06 a.m. |
| PD | Predicate disambiguation | batch_69deda7a95c48190bbe29fadcf17191a |
completed | April 15, 2026, 12:23 a.m. |
| PDg | Predicate description generation | batch_69dff7f05f708190850f1d8782e132b0 |
completed | April 15, 2026, 8:41 p.m. |
Created at: April 10, 2026, 4:06 a.m.