Triple
T23627411
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Valenciennes (1656) |
E583504
|
entity |
| Predicate | wasDefenceOf |
P6876
|
FINISHED |
| Object | Valenciennes |
E112910
|
NE 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: Valenciennes | Statement: [Battle of Valenciennes (1656), wasDefenceOf, Valenciennes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasDefenceOf Context triple: [Battle of Valenciennes (1656), wasDefenceOf, Valenciennes]
-
A.
defendedAs
Indicates that one entity is presented, argued, or justified as being equivalent to or serving the role of another entity in a defensive or protective context.
-
B.
defendedOn
Indicates that one entity protected, supported, or argued in favor of another entity during a specific time or event.
-
C.
defends
chosen
Indicates that one entity protects or supports another entity against attack, criticism, or harm.
-
D.
hasDefensivePurpose
Indicates that something exists or is designed with the primary goal of protection, defense, or safeguarding against threats or harm.
-
E.
defendedAtEvent
Indicates that an entity (typically a work, thesis, or position) was formally defended or argued for during a specific event.
- F. None of above.
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_69e248fc8d74819091bd5baef2f36f6f |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b1e4df248190ac38e4e025bd1140 |
completed | April 29, 2026, 7:23 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0fbce1b8308190826cb173c8b714ee |
completed | May 22, 2026, 2:18 a.m. |
| PD | Predicate disambiguation | batch_69f118d0e0588190a86527a7747c5427 |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:46 p.m.