Triple
T33654181
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | George Eacker |
E862176
|
entity |
| Predicate | dateOfDuelWithPhilipHamilton |
P94022
|
FINISHED |
| Object | November 23, 1801 |
—
|
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: November 23, 1801 | Statement: [George Eacker, dateOfDuelWithPhilipHamilton, November 23, 1801]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfDuelWithPhilipHamilton Context triple: [George Eacker, dateOfDuelWithPhilipHamilton, November 23, 1801]
-
A.
resultOfDuelWithPhilipHamilton
Indicates that something occurs as a consequence of, or is directly caused by, a duel involving Philip Hamilton.
-
B.
dateOfDuel
chosen
Indicates the specific calendar date on which a duel between the involved parties took place.
-
C.
allegedLocationOfDuel
Indicates the place where a duel is claimed or reported to have occurred, without confirming that it actually took place there.
-
D.
jawLostInDuelWith
Indicates that one entity lost their jaw as a result of a duel with another entity.
-
E.
reasonForDuel
Indicates the cause, motive, or triggering circumstance that led to the duel between the involved parties.
- 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_69f349840ba881908e3bfce536aeb92b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd2cf39b0c8190811b8a6fa9410560 |
completed | May 8, 2026, 12:23 a.m. |
| PD | Predicate disambiguation | batch_69fd2ad8dd988190a9899701ba00d917 |
completed | May 8, 2026, 12:14 a.m. |
Created at: May 1, 2026, 1:42 a.m.