Triple
T16839039
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | William Delaplace |
E409356
|
entity |
| Predicate | fortCapturedBy |
P105865
|
FINISHED |
| Object | American forces |
—
|
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: American forces | Statement: [William Delaplace, fortCapturedBy, American forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fortCapturedBy Context triple: [William Delaplace, fortCapturedBy, American forces]
-
A.
fortificationCaptured
chosen
Indicates that control of a defensive structure or fortified position has been taken from one party by another.
-
B.
wasRecapturedBy
Indicates that an entity which had previously escaped or been released was caught again by another entity.
-
C.
capturedOff
Indicates that one entity has taken another entity away or into custody, removing it from its original location or control.
-
D.
capturedForce
Indicates that one entity has taken control of another entity or group through force, restraint, or coercive action.
-
E.
capturedBy
Indicates that one entity has been seized, taken into control, or otherwise apprehended by another entity.
- 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_69d883952b048190887740a980b712ed |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b34f902c8190a334ba7caa04ce7e |
completed | April 18, 2026, 4:37 p.m. |
| PD | Predicate disambiguation | batch_69e32b87b4248190aaddb05e88452356 |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:23 a.m.