Triple
T33083368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leech |
E846565
|
entity |
| Predicate | powerEffectRange |
P65190
|
FINISHED |
| Object | short range |
—
|
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: short range | Statement: [Leech, powerEffectRange, short range]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: powerEffectRange Context triple: [Leech, powerEffectRange, short range]
-
A.
powerRangeRelativeTo
Indicates the comparative span or limits of power one entity has relative to another entity or reference standard.
-
B.
heroPowerEffect
Indicates the specific impact or outcome that a hero’s power has when it is used.
-
C.
powerLevel
Indicates the degree or intensity of power or strength possessed by an entity in a given context.
-
D.
powerRange
chosen
Indicates the range of power values within which an entity operates, applies, or is considered valid.
-
E.
usesPowerFor
Indicates that one entity applies or exploits a particular power, energy, or capability for a specific purpose or activity.
- 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_69f34954d46c8190a04a159cc5f99efd |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f78c61ed4c8190ad84c918fa9af55a |
completed | May 3, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69f78b8cb3a881909ebaac1b503988c2 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 1, 2026, 1:26 a.m.