Triple
T25730255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jamshoro |
E645219
|
entity |
| Predicate | roadBridgeCrossesTo |
P47919
|
FINISHED |
| Object | Hyderabad across the Indus 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: Hyderabad across the Indus River | Statement: [Jamshoro, roadBridgeCrossesTo, Hyderabad across the Indus River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadBridgeCrossesTo Context triple: [Jamshoro, roadBridgeCrossesTo, Hyderabad across the Indus River]
-
A.
riverCrossingStructure
chosen
Indicates a structure that allows passage across a river, such as by spanning or traversing it.
-
B.
bridgeType
Indicates the specific kind or classification of a bridge associated with an entity.
-
C.
tollBridge
Indicates that passage across a bridge requires payment of a toll or fee.
-
D.
hasBridgeCrossings
Indicates that one entity has one or more bridge structures that span across or connect over another entity (such as a road, river, or area).
-
E.
bridgeStructure
Indicates a structural relationship where one entity functions as a bridge that spans or connects two separate points or areas.
- 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_69e77e85254081908d79ee4e8715f283 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5fcbb125481909d97550556700576 |
completed | May 2, 2026, 1:31 p.m. |
| PD | Predicate disambiguation | batch_69f480824a1c81908a8a492eedbc2596 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 11:12 p.m.