Triple
T6118144
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siege of Paris |
E136411
|
entity |
| Predicate | blockadedBy |
P68236
|
FINISHED |
| Object | Prussian-led 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: Prussian-led forces | Statement: [Siege of Paris, blockadedBy, Prussian-led forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: blockadedBy Context triple: [Siege of Paris, blockadedBy, Prussian-led forces]
-
A.
blockadedIn
Indicates that one entity is prevented or obstructed by another from entering, leaving, or accessing a particular place or resource.
-
B.
blockadeType
Indicates the specific kind or category of blockade involved in the relationship or action.
-
C.
borderedBy
Indicates that one entity shares a common boundary or edge with another entity.
-
D.
detainedBy
Indicates that an entity is being held in custody or confinement by another entity, typically an authority or controlling party.
-
E.
sealedBy
Indicates that one entity is closed, secured, or made airtight/watertight through the action or presence of 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_69c0089f851c81909e5e189a617dcff6 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c05bec9b8c8190b3268b0ba952aae6 |
completed | March 22, 2026, 9:15 p.m. |
| PD | Predicate disambiguation | batch_69c049f9ab3c81909c8ab6466f6a2935 |
completed | March 22, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69c04e8e3f2c8190be459ca02f9b315a |
completed | March 22, 2026, 8:18 p.m. |
Created at: March 22, 2026, 4:14 p.m.