Triple
T38592404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blink (Overwatch ability) |
E932483
|
entity |
| Predicate | cannotBypass |
P193341
|
FINISHED |
| Object | solid barriers |
—
|
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: solid barriers | Statement: [Blink (Overwatch ability), cannotBypass, solid barriers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cannotBypass Context triple: [Blink (Overwatch ability), cannotBypass, solid barriers]
-
A.
cannotExceed
Indicates that one quantity, value, or limit must not be greater than another specified quantity or threshold.
-
B.
cannotRestrict
Indicates that one entity lacks the authority, ability, or right to impose limits, constraints, or prohibitions on another entity or its actions.
-
C.
cannotShow
Indicates that one entity is unable or not permitted to display, reveal, or present another entity.
-
D.
cannotVeto
Indicates that an entity lacks the authority or ability to reject, block, or override a decision, proposal, or action made by another entity.
-
E.
hasBypass
Indicates that one entity includes or is equipped with an alternative route or mechanism that circumvents or avoids another entity or process.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd4129a8848190a5002150278ac689 |
completed | May 8, 2026, 1:49 a.m. |
| PD | Predicate disambiguation | batch_69fd3e0515ec8190937c7af71ebc3875 |
completed | May 8, 2026, 1:36 a.m. |
| PDg | Predicate description generation | batch_69fd4128ed908190837ec9936774a1cf |
completed | May 8, 2026, 1:49 a.m. |
Created at: May 3, 2026, 4:32 p.m.