Triple
T12315190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hamilton City |
E293581
|
entity |
| Predicate | hasRiverCrossingType |
P104419
|
FINISHED |
| Object | 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: bridge | Statement: [Hamilton City, hasRiverCrossingType, bridge]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRiverCrossingType Context triple: [Hamilton City, hasRiverCrossingType, bridge]
-
A.
hasRiverCrossingNearby
Indicates that there is a river crossing located in close proximity to the referenced entity or location.
-
B.
hasBridgeTypeCrossing
Indicates that a bridge is characterized by a specific type of crossing it provides or supports.
-
C.
hasCanalCrossing
Indicates that one entity is connected to or traversed by another via a canal crossing, such as a bridge, aqueduct, or similar structure over a canal.
-
D.
riverCrossingConnection
Indicates a connection between two locations that are linked by a route or structure specifically used to cross a river.
-
E.
crossedByRiver
Indicates that a river passes across or through a specified area, feature, or route.
- 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_69d6ab6a2b50819082f6aedd32ed608a |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d93f621570819091ee1db2609233ea |
completed | April 10, 2026, 6:20 p.m. |
| PD | Predicate disambiguation | batch_69d93ec5be788190b82d2edc6a0f1095 |
completed | April 10, 2026, 6:17 p.m. |
| PDg | Predicate description generation | batch_69d93f607a88819089e89fd263ae9937 |
completed | April 10, 2026, 6:20 p.m. |
Created at: April 8, 2026, 9:53 p.m.