Triple
T34374486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Belfast |
E882249
|
entity |
| Predicate | typeOfBattle |
P161656
|
FINISHED |
| Object | set-piece battle |
—
|
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: set-piece battle | Statement: [Battle of Belfast, typeOfBattle, set-piece battle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfBattle Context triple: [Battle of Belfast, typeOfBattle, set-piece battle]
-
A.
fightType
chosen
Indicates the specific category or style of fight associated with an event or interaction between entities.
-
B.
battlegroundType
Indicates the specific kind or category of environment in which a battle or conflict takes place.
-
C.
battleFoughtBy
Indicates that a specific battle was fought by a particular participant or group of participants.
-
D.
battleOccurred
Indicates that a conflict or combat event took place between specified parties at a particular time and/or location.
-
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_69f349bf5d7481908dd5da4cbdf74047 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a01295195748190b896d99c3d1f6134 |
completed | May 11, 2026, 12:56 a.m. |
| PD | Predicate disambiguation | batch_6a0128fe96dc8190a73715ab08752dd1 |
completed | May 11, 2026, 12:55 a.m. |
Created at: May 1, 2026, 1:59 a.m.