Triple
T32356636
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Drewry’s Bluff |
E826748
|
entity |
| Predicate | artilleryEmplacementHeight |
P174181
|
FINISHED |
| Object | about 90 feet above the James River |
—
|
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: about 90 feet above the James River | Statement: [Battle of Drewry’s Bluff, artilleryEmplacementHeight, about 90 feet above the James River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: artilleryEmplacementHeight Context triple: [Battle of Drewry’s Bluff, artilleryEmplacementHeight, about 90 feet above the James River]
-
A.
artilleryAdvantage
Indicates that one side possesses a superior artillery capability or effectiveness compared to its opponent.
-
B.
artillerySupport
Indicates that one entity provides or coordinates artillery fire in support of another entity’s operations or objectives.
-
C.
artilleryRange
Indicates that one entity is within the effective firing distance of another entity’s artillery.
-
D.
artilleryType
Indicates the specific category or kind of artillery associated with an entity or event.
-
E.
artilleryWeight
Indicates the weight or mass associated with a piece of artillery in the relationship.
- 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_69f34915a2588190bb3178f5ec2f48f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6be602eec8190961d92f4db7d94a7 |
completed | May 3, 2026, 3:17 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6cef208190bc5cd43d96127004 |
completed | May 3, 2026, 3:01 a.m. |
| PDg | Predicate description generation | batch_69f6bbbe23d48190b2aa662d69b41900 |
completed | May 3, 2026, 3:06 a.m. |
Created at: May 1, 2026, 12:49 a.m.