Triple
T4178264
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Lincoln (1217) |
E86529
|
entity |
| Predicate | siegeContext |
P11070
|
FINISHED |
| Object | French and rebel forces were besieging Lincoln Castle |
—
|
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: French and rebel forces were besieging Lincoln Castle | Statement: [Battle of Lincoln (1217), siegeContext, French and rebel forces were besieging Lincoln Castle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: siegeContext Context triple: [Battle of Lincoln (1217), siegeContext, French and rebel forces were besieging Lincoln Castle]
-
A.
isSiegeOf
chosen
Indicates a relationship where one event or action constitutes the military siege of a particular place, target, or entity.
-
B.
siegeDuration
Indicates the length of time that a siege persists from its beginning to its end.
-
C.
opposedSiegeBy
Indicates that one party actively resisted, countered, or worked against another party’s siege.
-
D.
siegeStartDate
Indicates the calendar date on which a siege begins.
-
E.
besiegedIn
Indicates that one entity is under siege at, or during the event of, another specified location or time.
- 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_69aed93de98c8190ad838ce507b77c8a |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af07078cb081909f64326b12522410 |
completed | March 9, 2026, 5:44 p.m. |
| PD | Predicate disambiguation | batch_69af019155448190b19868583272513f |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:45 p.m.