Triple
T36505157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siege of Harfleur |
E899440
|
entity |
| Predicate | hasBesiegingForce |
P24785
|
FINISHED |
| Object | English expeditionary army of Henry V |
—
|
NE NERFINISHED |
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: English expeditionary army of Henry V | Statement: [Siege of Harfleur, hasBesiegingForce, English expeditionary army of Henry V]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBesiegingForce Context triple: [Siege of Harfleur, hasBesiegingForce, English expeditionary army of Henry V]
-
A.
hasBesiegingSide
Indicates that one party is the attacking or besieging side in a siege or military encirclement of another.
-
B.
wasBesiegedBy
Indicates that an entity (typically a place or stronghold) was subjected to a military siege carried out by another entity.
-
C.
besiegingForce
chosen
Indicates a military group that is surrounding and attacking a target location or force in an attempt to capture or subdue it.
-
D.
hasMajorSiege
Indicates that a significant or large-scale siege event occurred involving the related entities.
-
E.
isSiegeOf
Indicates a relationship where one event or action constitutes the military siege of a particular place, target, or 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_69f76e5b92088190933afda3f7531dd4 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd231cab588190ad0953dc8f4af8f2 |
completed | May 7, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69fd1aa3f1c481909fe6e9cab1383551 |
completed | May 7, 2026, 11:05 p.m. |
Created at: May 3, 2026, 4:10 p.m.