Triple
T33654186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | George Eacker |
E862176
|
entity |
| Predicate | legalStatusAfterDuel |
P109227
|
FINISHED |
| Object | not convicted of a crime |
—
|
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: not convicted of a crime | Statement: [George Eacker, legalStatusAfterDuel, not convicted of a crime]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalStatusAfterDuel Context triple: [George Eacker, legalStatusAfterDuel, not convicted of a crime]
-
A.
legalStatusOfDuel
Indicates the legal status or permissibility of engaging in a duel within a given jurisdiction or context.
-
B.
isClimacticDuelOf
Indicates that one event or confrontation serves as the decisive, peak showdown within the narrative arc of another event or storyline.
-
C.
statusAfterBattle
chosen
Indicates the condition or state of an entity following the completion of a battle or combat encounter.
-
D.
legalStatusAfterCoup
Indicates the legal status or standing of an entity following a coup or unconstitutional change of power.
-
E.
typeOfDuel
Indicates the specific kind or category of duel that characterizes a given dueling event or relationship between opponents.
- 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_69ff32b88bf48190b45afd1b60cb511c |
completed | May 9, 2026, 1:12 p.m. |
| PD | Predicate disambiguation | batch_69ff3031e18881908927b2ab452de863 |
completed | May 9, 2026, 1:01 p.m. |
Created at: May 1, 2026, 1:42 a.m.