Triple
T1311663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Esek Hopkins |
E28004
|
entity |
| Predicate | causeOfEndOfCommand |
P11350
|
FINISHED |
| Object | dismissal by Continental Congress |
—
|
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: dismissal by Continental Congress | Statement: [Esek Hopkins, causeOfEndOfCommand, dismissal by Continental Congress]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfEndOfCommand Context triple: [Esek Hopkins, causeOfEndOfCommand, dismissal by Continental Congress]
-
A.
reasonForExecution
Indicates that one entity specifies the cause, motive, or justification for carrying out the execution of another entity or action.
-
B.
causeOf
Indicates that one entity brings about, produces, or is responsible for the occurrence or existence of another entity or event.
-
C.
removedFromCommandBy
Indicates that one entity was taken out of a position of command or authority by another entity.
-
D.
reasonForDiscontinuation
chosen
Indicates that one entity specifies the cause or justification for stopping, ending, or withdrawing another entity, process, or activity.
-
E.
commandedBy
Indicates that one entity holds authoritative control or issues orders over another entity.
- 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_69a498532c3481909223b74af2e578df |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c1560f888190bdd9107b08395e0b |
completed | March 1, 2026, 10:44 p.m. |
| PD | Predicate disambiguation | batch_69a4bee9e4a88190b22ab2ee831a23c9 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:55 p.m.