Triple
T8595428
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of High Bridge |
E203531
|
entity |
| Predicate | hasSiteStatus |
P83767
|
FINISHED |
| Object | partially preserved battlefield area |
—
|
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: partially preserved battlefield area | Statement: [Battle of High Bridge, hasSiteStatus, partially preserved battlefield area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSiteStatus Context triple: [Battle of High Bridge, hasSiteStatus, partially preserved battlefield area]
-
A.
hasSiteStatusAtStart
Indicates that an entity possesses a particular site status at the beginning of a specified period or event.
-
B.
hasSiteUse
Indicates that a site is used or designated for a particular function, activity, or purpose.
-
C.
hasSiteCode
Indicates that an entity is associated with a specific site identifier or code used to distinguish its location or facility.
-
D.
websiteStatus
Indicates the current operational condition or availability state of a website.
-
E.
hasAdministrationSite
Indicates the specific location or site on or in a subject where a substance, treatment, or intervention is administered.
- 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_69ca832a7f108190b4e4f5648abf4aa2 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cc46c76fd48190ae67b660c5b8e29f |
completed | March 31, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69cc454504448190aaad2af8b17357cd |
completed | March 31, 2026, 10:05 p.m. |
| PDg | Predicate description generation | batch_69cc46c330bc8190a9b644078881c6ff |
completed | March 31, 2026, 10:12 p.m. |
Created at: March 30, 2026, 6:23 p.m.