Triple
T26493889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Special Order 191 |
E669227
|
entity |
| Predicate | orderedOperationAgainst |
P116347
|
FINISHED |
| Object | Harpers Ferry |
—
|
NE NERFINISHED |
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: Harpers Ferry | Statement: [Special Order 191, orderedOperationAgainst, Harpers Ferry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: orderedOperationAgainst Context triple: [Special Order 191, orderedOperationAgainst, Harpers Ferry]
-
A.
commandedOperationAgainst
chosen
Indicates that one entity issued authoritative orders to initiate or conduct a specific military or strategic operation directed against another entity.
-
B.
opposedOperation
Indicates that one operation is in conflict with, counters, or works against another operation.
-
C.
operationOf
Indicates that one entity is the function, activity, or process carried out by another entity (such as a system, device, or organization).
-
D.
inOperation
Indicates that an entity (such as a system, device, or facility) is currently active, functioning, and performing its intended operation.
-
E.
orden
Indicates that one entity issues, gives, or establishes an order, command, or directive concerning another entity or situation.
- 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_69eeb319007081909642b414b114b35a |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f65aa07c048190a5df30d53d8f0cf5 |
completed | May 2, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f659cc571c819097e51e531961d812 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 27, 2026, 1:06 a.m.