Triple
T10414349
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Philip Hamilton |
E245477
|
entity |
| Predicate | dateOfDuel |
P94022
|
FINISHED |
| Object | 1801-11-23 |
—
|
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: 1801-11-23 | Statement: [Philip Hamilton, dateOfDuel, 1801-11-23]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfDuel Context triple: [Philip Hamilton, dateOfDuel, 1801-11-23]
-
A.
allegedLocationOfDuel
Indicates the place where a duel is claimed or reported to have occurred, without confirming that it actually took place there.
-
B.
typeOfDuel
Indicates the specific kind or category of duel that characterizes a given dueling event or relationship between opponents.
-
C.
battleOccurredOn
Indicates that a specific battle took place at or on a particular location or date.
-
D.
dateOfVictory
Indicates the specific calendar date on which a victory or winning outcome occurred.
-
E.
battleDateRelation
Indicates the temporal relationship specifying on which date a particular battle or combat event took place.
- 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_69d381be340c8190b05998703d42d224 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4ea0ec6fc8190a71af759226a3cba |
completed | April 7, 2026, 11:27 a.m. |
| PD | Predicate disambiguation | batch_69d4dfb6f160819090040644a12395ec |
completed | April 7, 2026, 10:43 a.m. |
| PDg | Predicate description generation | batch_69d4e91ce2008190af252c140370b7f2 |
completed | April 7, 2026, 11:23 a.m. |
Created at: April 6, 2026, 12:10 p.m.