Triple
T23627414
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Valenciennes (1656) |
E583504
|
entity |
| Predicate | wasRepulsedBy |
P4567
|
FINISHED |
| Object | Spanish 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: Spanish forces | Statement: [Battle of Valenciennes (1656), wasRepulsedBy, Spanish forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasRepulsedBy Context triple: [Battle of Valenciennes (1656), wasRepulsedBy, Spanish forces]
-
A.
resistedIn
Indicates that an entity actively opposed, withstood, or fought against something within a specific context, event, or location.
-
B.
opposedBy
Indicates that one entity actively resists, disagrees with, or works against the actions, views, or position of another entity.
-
C.
wasFirstToRefuse
Indicates that an entity was the earliest among a group to decline or reject something.
-
D.
repudiatedAfter
Indicates that one entity formally rejects, disavows, or withdraws support for another entity after a specified time or subsequent event.
-
E.
opposingForce
chosen
Indicates a relationship where one entity actively resists, counters, or works against the actions, goals, or influence of 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_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.