Triple
T23663722
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | English Civil War sieges of Pontefract Castle |
E584518
|
entity |
| Predicate | finalSurrenderDate |
P4667
|
FINISHED |
| Object | March 1649 |
—
|
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: March 1649 | Statement: [English Civil War sieges of Pontefract Castle, finalSurrenderDate, March 1649]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalSurrenderDate Context triple: [English Civil War sieges of Pontefract Castle, finalSurrenderDate, March 1649]
-
A.
surrenderDate
chosen
Indicates the date on which an entity formally yields control, possession, or rights, typically ending its claim or resistance.
-
B.
finalDefeatDate
Indicates the date on which an entity was ultimately and conclusively defeated.
-
C.
finalShutdownDate
Indicates the date on which an entity is permanently shut down or ceases operation.
-
D.
surrenderedAfter
Indicates that one entity surrendered following or as a consequence of another specified event, action, or time.
-
E.
surrenderEffectiveTime
Indicates the point in time at which a surrender (e.g., of rights, ownership, or an agreement) becomes legally or practically effective.
- 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_69e24901421881908c17a5293bdd4a8e |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b40a1284819087cd29c9c390549d |
completed | April 29, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69f118dd13008190a8799b4e9cadbd79 |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:50 p.m.