Triple
T32763240
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cobb’s Brigade marker |
E837813
|
entity |
| Predicate | locatedOnBattlefield |
P121570
|
FINISHED |
| Object | Fredericksburg battlefield |
E778651
|
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: Fredericksburg battlefield | Statement: [Cobb’s Brigade marker, locatedOnBattlefield, Fredericksburg battlefield]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedOnBattlefield Context triple: [Cobb’s Brigade marker, locatedOnBattlefield, Fredericksburg battlefield]
-
A.
positionInBattle
Indicates the specific role or placement an entity occupies within the formation or structure of a battle.
-
B.
battlefieldLocatedIn
Indicates that a battlefield is situated within or belongs to a specific geographic or administrative location.
-
C.
battlefieldOf
Indicates that a location is the site where a particular battle or military engagement took place.
-
D.
locationOnField
chosen
Indicates the specific position or area that an entity occupies on a defined field or playing surface.
-
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 (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_69f34939857c8190aa9970c51feec1eb |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a0317eaf4e88190a6f6419cb4ef7547 |
completed | May 12, 2026, 12:07 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a34a7c3bbac8190a7aebc5e36b8b780 |
completed | June 19, 2026, 2:21 a.m. |
| PD | Predicate disambiguation | batch_6a03179da394819095e3d346c3785d74 |
completed | May 12, 2026, 12:05 p.m. |
Created at: May 1, 2026, 1:13 a.m.