Triple
T38337104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Rich Mountain |
E1037986
|
entity |
| Predicate | preservedSite |
P195850
|
FINISHED |
| Object | Rich Mountain 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: Rich Mountain Battlefield | Statement: [Battle of Rich Mountain, preservedSite, Rich Mountain Battlefield]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preservedSite Context triple: [Battle of Rich Mountain, preservedSite, Rich Mountain Battlefield]
-
A.
preservedAt
Indicates that something is kept, maintained, or conserved in a particular place or context.
-
B.
preservedFor
Indicates that something has been kept intact or maintained in a particular state for the benefit, use, or reference of a specified entity or purpose.
-
C.
preservedFrom
Indicates that something has been protected or kept safe from a particular source of damage, loss, or alteration.
-
D.
preservedWith
Indicates that one entity is kept intact, maintained, or protected by means of another entity used as a preservative or preservation method.
-
E.
preservedUnder
Indicates that a certain property, structure, or relation remains unchanged when a specified transformation, operation, or process is applied.
- F. None of above. chosen
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_69f76e20d65c81909619ac0dd85c56f0 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fde9fc184c8190bebef35df0e76076 |
completed | May 8, 2026, 1:49 p.m. |
| PD | Predicate disambiguation | batch_69fde6e5beb4819094945a695e961d88 |
completed | May 8, 2026, 1:36 p.m. |
| PDg | Predicate description generation | batch_69fde9fb68388190ada4a7018e2a2f76 |
completed | May 8, 2026, 1:49 p.m. |
Created at: May 3, 2026, 4:30 p.m.