Triple
T10957487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fifty-Four Forty or Fight |
E258882
|
entity |
| Predicate | impliesRiskOf |
P94557
|
FINISHED |
| Object | war with Britain |
—
|
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: war with Britain | Statement: [Fifty-Four Forty or Fight, impliesRiskOf, war with Britain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: impliesRiskOf Context triple: [Fifty-Four Forty or Fight, impliesRiskOf, war with Britain]
-
A.
hasImplicationsFor
chosen
Indicates that one entity’s state, action, or condition leads to consequences, effects, or relevance for another entity.
-
B.
riskElement
Indicates that one entity is a risk-related component, factor, or contributor associated with another entity within a risk context.
-
C.
riskIfNoncompliance
Indicates that a risk or negative consequence will occur if the specified rules, requirements, or obligations are not complied with.
-
D.
riskTaken
Indicates that an entity has undertaken an action or decision involving exposure to potential loss, harm, or uncertainty.
-
E.
riskType
Indicates the category or nature of risk associated with an entity, event, or relationship.
- 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_69d6aa88500c819097d7032ca578e74f |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d771260e9881909401a7a7466e1b8a |
completed | April 9, 2026, 9:28 a.m. |
| PD | Predicate disambiguation | batch_69d72e874f48819096ffa878f90c7d5b |
completed | April 9, 2026, 4:43 a.m. |
Created at: April 8, 2026, 9:23 p.m.