Triple
T10547343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Savage, Maryland |
E248854
|
entity |
| Predicate | hasHistoricBridgeType |
P1738
|
FINISHED |
| Object | wrought-iron truss bridge |
—
|
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: wrought-iron truss bridge | Statement: [Savage, Maryland, hasHistoricBridgeType, wrought-iron truss bridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricBridgeType Context triple: [Savage, Maryland, hasHistoricBridgeType, wrought-iron truss bridge]
-
A.
hasTypeHistory
Indicates that an entity is associated with a record or sequence of its past and present types or classifications over time.
-
B.
hasBuildingTypeOnBridge
Indicates that a specific type of building or structure is located on or constructed upon a bridge.
-
C.
hasBridgeTo
Indicates that one entity is connected to another by a bridge or bridging structure that allows passage or linkage between them.
-
D.
hasBridges
Indicates that one entity possesses, contains, or is characterized by one or more bridges connecting locations or components.
-
E.
hasNotableBridgeType
chosen
Indicates that an entity is associated with a specific, noteworthy type or design category of bridge.
- 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_69d381c733c08190ab1dd6239f5f34ae |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d52710869c81909b6db1a190825bad |
completed | April 7, 2026, 3:47 p.m. |
| PD | Predicate disambiguation | batch_69d518fa0b4081909bffc936d78bd77b |
completed | April 7, 2026, 2:47 p.m. |
Created at: April 6, 2026, 12:33 p.m.