Triple
T11010218
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siege of Harfleur |
E260225
|
entity |
| Predicate | garrisonSurrenderedOn |
P23230
|
FINISHED |
| Object | 1415-09-22 |
—
|
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: 1415-09-22 | Statement: [Siege of Harfleur, garrisonSurrenderedOn, 1415-09-22]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: garrisonSurrenderedOn Context triple: [Siege of Harfleur, garrisonSurrenderedOn, 1415-09-22]
-
A.
garrisonSurrenderedTo
Indicates that a defending military garrison formally capitulated and yielded control to another party.
-
B.
dateOfCityCapture
Indicates the specific date on which a city was taken or captured, typically in a military or political context.
-
C.
siegeEndDate
chosen
Indicates the date on which a siege concluded or was lifted.
-
D.
placeOfSurrender
Indicates the location where an entity formally surrendered to another party.
-
E.
surrenderedIn
Indicates that an entity yielded or gave up control, power, or resistance within a specific event, context, or situation.
- 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_69d6aa9687448190b28d353b1b6a610e |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d79788d44c819084f35693ed96f422 |
completed | April 9, 2026, 12:11 p.m. |
| PD | Predicate disambiguation | batch_69d72e96be6c8190a46c69f61b2d8cd4 |
completed | April 9, 2026, 4:44 a.m. |
Created at: April 8, 2026, 9:25 p.m.