Triple
T14267837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hubbardton, Vermont |
E353696
|
entity |
| Predicate | battleSignificance |
P70569
|
FINISHED |
| Object | only Revolutionary War battle fought entirely on Vermont soil |
—
|
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: only Revolutionary War battle fought entirely on Vermont soil | Statement: [Hubbardton, Vermont, battleSignificance, only Revolutionary War battle fought entirely on Vermont soil]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: battleSignificance Context triple: [Hubbardton, Vermont, battleSignificance, only Revolutionary War battle fought entirely on Vermont soil]
-
A.
hasSignificantBattle
Indicates that a major or decisive battle occurred involving the related entities.
-
B.
notableBattleRecognized
Indicates that a particular battle is formally acknowledged or recognized as notable in relation to the subject.
-
C.
hasMilitarySignificance
Indicates that something holds strategic or tactical importance for military planning, operations, or defense objectives.
-
D.
battleDepicted
Indicates that a work or representation visually portrays a specific battle or combat event.
-
E.
notableBattlefield
chosen
Indicates that a location is recognized as the site of a historically significant battle or military engagement.
- 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_69d8278d25148190abf1a8c8f5f533ad |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de6358c2288190ac1fd26e688a605d |
completed | April 14, 2026, 3:55 p.m. |
| PD | Predicate disambiguation | batch_69de2a7d586c8190846ff242bbf5ac53 |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:10 a.m.