Triple
T29820409
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Nantes (1793) |
E757228
|
entity |
| Predicate | goalOfRoyalists |
P21103
|
FINISHED |
| Object | capture 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: capture of Nantes | Statement: [Battle of Nantes (1793), goalOfRoyalists, capture of Nantes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: goalOfRoyalists Context triple: [Battle of Nantes (1793), goalOfRoyalists, capture of Nantes]
-
A.
royalistObjective
chosen
Indicates that an entity’s goal, purpose, or intended outcome is to support, preserve, or advance a monarchy or royal authority.
-
B.
royalistTactic
Indicates a tactic, strategy, or method employed by royalists in support of a monarchy or royal authority.
-
C.
consideredByRoyalistsAs
Indicates that something or someone is regarded or judged in a particular way by royalists.
-
D.
RoyalistSide
Indicates that an entity is aligned with, supports, or belongs to the faction favoring a monarchy or royal authority in a given conflict or context.
-
E.
royalistForcesCharacteristic
Indicates that a characteristic, trait, or attribute is associated specifically with royalist forces.
- 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_69f66ac1a4fc81909740d2e52fbe6970 |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 29, 2026, 5:28 p.m.