Triple
T9233499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siege of Belfort |
E221878
|
entity |
| Predicate | surrenderTerms |
P87711
|
FINISHED |
| Object | French garrison allowed to march out with honors of war |
—
|
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 garrison allowed to march out with honors of war | Statement: [Siege of Belfort, surrenderTerms, French garrison allowed to march out with honors of war]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: surrenderTerms Context triple: [Siege of Belfort, surrenderTerms, French garrison allowed to march out with honors of war]
-
A.
requiredSurrenderOf
Indicates that one party is obligated to give up or relinquish something to another party.
-
B.
surrenderAcceptedBy
Indicates that one party’s act of surrender is formally received and agreed to by another party.
-
C.
surrenderedAfter
Indicates that one entity surrendered following or as a consequence of another specified event, action, or time.
-
D.
surrenderSignedWith
Indicates that a formal act of surrender has been signed between two parties, establishing the end of hostilities or conflict between them.
-
E.
termOfService
Indicates that one entity defines or specifies the terms of service (rules, conditions, and usage policies) that apply to another entity.
- F. None of above. chosen
Provenance (4 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_69ca83ed628c8190bc02d641e57f097f |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccee1baa3c8190870d1e850ccab1e0 |
completed | April 1, 2026, 10:06 a.m. |
| PD | Predicate disambiguation | batch_69cc7a3daeb481908b0abde3fbc1f1f0 |
completed | April 1, 2026, 1:51 a.m. |
| PDg | Predicate description generation | batch_69cc95597be081908ece2491dd2f0f74 |
completed | April 1, 2026, 3:47 a.m. |
Created at: March 30, 2026, 7:29 p.m.