Triple
T23627412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Valenciennes (1656) |
E583504
|
entity |
| Predicate | isSiegeRelated |
P101059
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Battle of Valenciennes (1656), isSiegeRelated, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSiegeRelated Context triple: [Battle of Valenciennes (1656), isSiegeRelated, yes]
-
A.
isSiegeOf
Indicates a relationship where one event or action constitutes the military siege of a particular place, target, or entity.
-
B.
siegeRelated
chosen
Indicates a relationship in which one entity is involved with, associated with, or relevant to a siege or siege-related activities.
-
C.
opposedSiegeBy
Indicates that one party actively resisted, countered, or worked against another party’s siege.
-
D.
typeOfSiege
Indicates the specific kind or category of siege involved in a conflict or military operation.
-
E.
siegeOccurredIn
Indicates that a siege took place within or at the location specified by the related 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_69e248fc8d74819091bd5baef2f36f6f |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b1e4df248190ac38e4e025bd1140 |
completed | April 29, 2026, 7:23 a.m. |
| PD | Predicate disambiguation | batch_69f118d0e0588190a86527a7747c5427 |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:46 p.m.