Triple
T24951702
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint-Privat |
E624355
|
entity |
| Predicate | partOfBattlefield |
P162197
|
FINISHED |
| Object | Gravelotte–Saint-Privat battlefield |
—
|
NE NERFINISHED |
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: Gravelotte–Saint-Privat battlefield | Statement: [Saint-Privat, partOfBattlefield, Gravelotte–Saint-Privat battlefield]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfBattlefield Context triple: [Saint-Privat, partOfBattlefield, Gravelotte–Saint-Privat battlefield]
-
A.
battlefieldSector
Indicates a specific area or zone of a battlefield in which a military unit, action, or event is located or occurs.
-
B.
battlefieldOf
Indicates that a location is the site where a particular battle or military engagement took place.
-
C.
battlefieldLocatedIn
chosen
Indicates that a battlefield is situated within or belongs to a specific geographic or administrative location.
-
D.
battlePartOf
Indicates that a specific battle is a component or segment of a larger military campaign, war, or conflict.
-
E.
primaryBattlefieldOf
Indicates that a specified location serves as the main or most significant battlefield where a particular conflict or war primarily took place.
- 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_69e2ff22e4c48190a0444b5a044f14e8 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651a731508190bb0c8c2462eba224 |
completed | May 2, 2026, 7:33 p.m. |
Created at: April 18, 2026, 5:57 a.m.