Triple
T29820410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Nantes (1793) |
E757228
|
entity |
| Predicate | goalOfRepublicans |
P127127
|
FINISHED |
| Object | defense of Nantes |
—
|
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: defense of Nantes | Statement: [Battle of Nantes (1793), goalOfRepublicans, defense of Nantes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: goalOfRepublicans Context triple: [Battle of Nantes (1793), goalOfRepublicans, defense of Nantes]
-
A.
republicanParty
Indicates that an entity is affiliated with, belongs to, or is a member/supporter of the Republican Party.
-
B.
outcomeForRepublicans
Indicates the result or consequence that an event, action, or situation has specifically for Republicans.
-
C.
objectiveOfRepublicanForces
chosen
Indicates that a specified goal, target, or aim is pursued or held by Republican forces.
-
D.
goalOfReforms
Indicates that a reform or set of reforms is undertaken with the aim or intended objective of achieving a particular outcome.
-
E.
constitutionalGoal
Indicates that something serves as a fundamental objective or guiding principle established by a constitution.
- 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_69f2245701c88190ad42415a0956c4ed |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6756645d48190a1645d578759dccd |
completed | May 2, 2026, 10:06 p.m. |
| PD | Predicate disambiguation | batch_69f66ec5bf508190ad088b89455252bd |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 5:28 p.m.