Triple
T7607519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Fishing Creek |
E180144
|
entity |
| Predicate | surpriseAttack |
P77747
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Battle of Fishing Creek, surpriseAttack, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: surpriseAttack Context triple: [Battle of Fishing Creek, surpriseAttack, true]
-
A.
spinAttackEffect
Indicates an effect that occurs when an entity performs or is subjected to a spinning attack action.
-
B.
counterattackBy
Indicates that an entity launches a retaliatory attack in response to an initial attack carried out by another entity.
-
C.
notableAttack
Indicates that an entity carried out, was involved in, or is strongly associated with a particularly significant or well-known attack.
-
D.
attackType
Indicates the specific method, style, or category of attack used in an aggressive or hostile action between entities.
-
E.
attackedFrom
Indicates that one entity initiated an attack against another entity originating from a specific source location or position.
- 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_69c69f3567008190ab01d2ca7b53584a |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c6fa1de8a4819091f9e9347835ce16 |
completed | March 27, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e485f88190910b39da52a955fe |
completed | March 27, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69c6f8195e5c8190835e28d44e19f6ef |
completed | March 27, 2026, 9:35 p.m. |
Created at: March 27, 2026, 3:54 p.m.