Triple
T29655002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colossus |
E750240
|
entity |
| Predicate | attackRange |
P100775
|
FINISHED |
| Object | long-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: long-range | Statement: [Colossus, attackRange, long-range]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attackRange Context triple: [Colossus, attackRange, long-range]
-
A.
attackEffect
Indicates that one entity’s attack produces a specific effect or consequence on another entity.
-
B.
attackType
Indicates the specific method, style, or category of attack used in an aggressive or hostile action between entities.
-
C.
hasFiringRange
Indicates that one entity possesses or provides a designated area or capability for discharging weapons over a specified distance.
-
D.
hostilityRange
chosen
Indicates the distance within which an entity will treat another as a hostile target and may initiate or respond with aggressive actions.
-
E.
attackFeasibility
Indicates the extent to which carrying out an attack is practically possible given current conditions, capabilities, and constraints.
- 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_69f0d6226fe881908819197c9ef9ee04 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec5bf508190ad088b89455252bd |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 28, 2026, 6:54 p.m.