Triple
T29413542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of High Bridge |
E745960
|
entity |
| Predicate | railroadBridge |
P117228
|
FINISHED |
| Object | High Bridge |
—
|
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: High Bridge | Statement: [Battle of High Bridge, railroadBridge, High Bridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: railroadBridge Context triple: [Battle of High Bridge, railroadBridge, High Bridge]
-
A.
hasRailBridge
chosen
Indicates that one location or structure is connected to another by a bridge specifically designed to carry railway tracks or trains.
-
B.
bridgeStructure
Indicates a structural relationship where one entity functions as a bridge that spans or connects two separate points or areas.
-
C.
bridgeType
Indicates the specific kind or classification of a bridge associated with an entity.
-
D.
riverCrossingStructure
Indicates a structure that allows passage across a river, such as by spanning or traversing it.
-
E.
hasPassengerBridge
Indicates that one entity is connected to another by a bridge or walkway specifically designed for passengers to move between them.
- 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_69f0a79f6d5c8190a350baed0157e06f |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f66a3b1e108190bec0049dc39f8926 |
completed | May 2, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69f66339175c819080bd70f0ff7057b1 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 2:59 p.m.