Triple
T26092824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corkscrew Conk |
E658171
|
entity |
| Predicate | attackDirection |
P9783
|
FINISHED |
| Object | downward |
—
|
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: downward | Statement: [Corkscrew Conk, attackDirection, downward]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attackDirection Context triple: [Corkscrew Conk, attackDirection, downward]
-
A.
attackType
Indicates the specific method, style, or category of attack used in an aggressive or hostile action between entities.
-
B.
primaryAdversaryDirection
Indicates the direction from an entity toward its main or most significant adversary.
-
C.
attackedFrom
Indicates that one entity initiated an attack against another entity originating from a specific source location or position.
-
D.
attackEffect
Indicates that one entity’s attack produces a specific effect or consequence on another entity.
-
E.
forceDirection
chosen
Indicates the direction in which a force is applied or exerted in the relationship between entities.
- 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_69ee5bbfc4d08190a1b206d0ac3a1e8d |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f607335d60819081808e1a52941262 |
completed | May 2, 2026, 2:16 p.m. |
| PD | Predicate disambiguation | batch_69f5b0021da88190bdd4cf2698c23edf |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 26, 2026, 7:48 p.m.