Triple
T291925
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | James II of England |
E6011
|
entity |
| Predicate | sideInBattleOfTheBoyne |
P375
|
FINISHED |
| Object | Jacobite |
—
|
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: Jacobite | Statement: [James II of England, sideInBattleOfTheBoyne, Jacobite]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sideInBattleOfTheBoyne Context triple: [James II of England, sideInBattleOfTheBoyne, Jacobite]
-
A.
conflictSide
chosen
Indicates that an entity participates as a distinct party or faction on one side of a conflict or dispute.
-
B.
historicallyContestedBy
Indicates that two or more parties have disputed or challenged control, ownership, or interpretation of something over a period of history.
-
C.
conflictBelligerent
Indicates that an entity is a participating belligerent (e.g., a country, group, or force) in a specific conflict.
-
D.
side
Indicates that one entity is located at, aligned with, or associated with the lateral part or edge of another entity.
-
E.
opposingForce
Indicates a relationship where one entity actively resists, counters, or works against the actions, goals, or influence of another entity.
- 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_69a2e79114b081909490b3bf5a5dbb51 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2ea0dd1dc8190aecd5afdeb2fd74b |
completed | Feb. 28, 2026, 1:13 p.m. |
| PD | Predicate disambiguation | batch_69a2e934b4408190b53a17f57a02df65 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:06 p.m.