Triple
T26346317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Van Terminator |
E662784
|
entity |
| Predicate | impactCharacteristic |
P51728
|
FINISHED |
| Object | high-impact strike |
—
|
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: high-impact strike | Statement: [Van Terminator, impactCharacteristic, high-impact strike]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: impactCharacteristic Context triple: [Van Terminator, impactCharacteristic, high-impact strike]
-
A.
impactDescription
Indicates a description of the effect, consequence, or influence that one entity, action, or event has on another.
-
B.
impactFeatureName
Indicates that one entity has an effect on, or causes a change in, a specific feature or characteristic identified by name in another entity or context.
-
C.
valueCharacteristic
Indicates that one entity serves as a value or specific quantitative/qualitative measure that characterizes or describes another entity.
-
D.
impactCategory
chosen
Indicates the type or domain of effect that one entity or action has on another, classifying the nature of its impact.
-
E.
impactStatus
Indicates the current state or condition of how something has affected or influenced a target.
- 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_69ee81304194819092e20e0fae3aee07 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f6640168948190811bd5f933a87cf5 |
completed | May 2, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69f6633451948190bcc0410602bb4914 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 26, 2026, 10:42 p.m.