Triple
T1042481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Williamite War in Ireland |
E22497
|
entity |
| Predicate | FrenchRole |
P23853
|
FINISHED |
| Object | military aid to Jacobites |
—
|
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: military aid to Jacobites | Statement: [Williamite War in Ireland, FrenchRole, military aid to Jacobites]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: FrenchRole Context triple: [Williamite War in Ireland, FrenchRole, military aid to Jacobites]
-
A.
FrenchCommander
Indicates that an entity serves as a military commander associated with France.
-
B.
FrenchObjective
Indicates that an entity serves as the goal, target, or object of an action or relation specifically within a French linguistic or contextual framework.
-
C.
FrenchCasualties
Indicates that the relationship specifies the number or extent of casualties suffered by French forces in a given event or context.
-
D.
hasFrenchSector
Indicates that an entity includes, controls, or is associated with a sector or area designated as French.
-
E.
nameInFrench
Indicates that an entity is known or referred to by a specific name expressed in the French language.
- 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_69a493d91478819094cc01fb65564bc1 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b845fa8c8190a7b69629883b62e2 |
completed | March 1, 2026, 10:05 p.m. |
| PD | Predicate disambiguation | batch_69a4b72ba60881908b017ef3b2b9645e |
completed | March 1, 2026, 10:01 p.m. |
| PDg | Predicate description generation | batch_69a4b8444f708190815732408aa0463e |
completed | March 1, 2026, 10:05 p.m. |
Created at: March 1, 2026, 7:42 p.m.