Triple
T17731731
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siege of Fort Vaux |
E442601
|
entity |
| Predicate | causeOfSurrender |
P128787
|
FINISHED |
| Object | exhaustion of water supplies |
—
|
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: exhaustion of water supplies | Statement: [Siege of Fort Vaux, causeOfSurrender, exhaustion of water supplies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfSurrender Context triple: [Siege of Fort Vaux, causeOfSurrender, exhaustion of water supplies]
-
A.
resultOfSurrender
Indicates that something exists or occurs as a consequence or outcome of a surrender event or act of capitulation.
-
B.
termsOfSurrender
Indicates the conditions and obligations agreed upon by parties when one side formally yields or capitulates to another.
-
C.
surrenderedAfter
Indicates that one entity surrendered following or as a consequence of another specified event, action, or time.
-
D.
timeOfSurrender
Indicates the specific point in time at which an entity formally surrenders or yields.
-
E.
reasonForForfeiture
Indicates the cause or justification that led to something being surrendered, lost, or taken away.
- 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_69d8b9ec79688190b86bdcef85a7b3aa |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e478e7773081909dadb90ff5cb0906 |
completed | April 19, 2026, 6:40 a.m. |
| PD | Predicate disambiguation | batch_69e3cde815e08190881972e2d80d151e |
completed | April 18, 2026, 6:31 p.m. |
| PDg | Predicate description generation | batch_69e3d37ab6988190bd326ea6f8dd4aaa |
completed | April 18, 2026, 6:54 p.m. |
Created at: April 10, 2026, 10:08 a.m.