Triple
T36505173
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siege of Harfleur |
E899440
|
entity |
| Predicate | hasSurrenderTerms |
P96989
|
FINISHED |
| Object | town to surrender if not relieved by a set date |
—
|
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: town to surrender if not relieved by a set date | Statement: [Siege of Harfleur, hasSurrenderTerms, town to surrender if not relieved by a set date]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSurrenderTerms Context triple: [Siege of Harfleur, hasSurrenderTerms, town to surrender if not relieved by a set date]
-
A.
surrenderTerms
Indicates the conditions or stipulations under which one party formally yields or capitulates to another.
-
B.
requiredSurrenderOf
Indicates that one party is obligated to give up or relinquish something to another party.
-
C.
termsOfSurrender
chosen
Indicates the conditions and obligations agreed upon by parties when one side formally yields or capitulates to another.
-
D.
typeOfSurrender
Indicates the specific manner or category of surrender that characterizes how one party yields or gives up to another.
-
E.
hasTermsOfUse
Indicates that an entity is associated with or governed by specific terms of use.
- 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_6a0019b0e9fc81909494320f05e81742 |
completed | May 10, 2026, 5:37 a.m. |
| PD | Predicate disambiguation | batch_6a00193379e0819096d1985686ce10e3 |
completed | May 10, 2026, 5:35 a.m. |
Created at: May 3, 2026, 4:10 p.m.