Triple
T32447932
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | First Siege of Ciudad Rodrigo (1810) |
E829195
|
entity |
| Predicate | fortressCapturedBy |
P105865
|
FINISHED |
| Object | French forces under Marshal Ney |
—
|
NE NERFINISHED |
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 forces under Marshal Ney | Statement: [First Siege of Ciudad Rodrigo (1810), fortressCapturedBy, French forces under Marshal Ney]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fortressCapturedBy Context triple: [First Siege of Ciudad Rodrigo (1810), fortressCapturedBy, French forces under Marshal Ney]
-
A.
fortificationCaptured
chosen
Indicates that control of a defensive structure or fortified position has been taken from one party by another.
-
B.
fortressDefended
Indicates that a fortress is actively protected against threats or attacks by some defending force.
-
C.
fortificationTypeAssaulted
Indicates that an assault or attack was carried out against a specific type of fortification.
-
D.
capturedForce
Indicates that one entity has taken control of another entity or group through force, restraint, or coercive action.
-
E.
wasRecapturedBy
Indicates that an entity which had previously escaped or been released was caught again 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_69f3491d2e5c819092b1c9535beff8ec |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c2e767bc8190b49fd0c4a557b464 |
completed | May 3, 2026, 3:37 a.m. |
| PD | Predicate disambiguation | batch_69f6ba700a708190ab6db62791e43774 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:56 a.m.