Triple
T8021887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Attock |
E186757
|
entity |
| Predicate | riverCrossingFunction |
P80616
|
FINISHED |
| Object | major crossing point over 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: major crossing point over the Indus River | Statement: [Attock, riverCrossingFunction, major crossing point over the Indus River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riverCrossingFunction Context triple: [Attock, riverCrossingFunction, major crossing point over the Indus River]
-
A.
riverCrossingConnection
Indicates a connection between two locations that are linked by a route or structure specifically used to cross a river.
-
B.
hasBridgeTypeCrossing
Indicates that a bridge is characterized by a specific type of crossing it provides or supports.
-
C.
crossedByRiver
Indicates that a river passes across or through a specified area, feature, or route.
-
D.
hasMethodOfCrossing
Indicates that one entity uses or is associated with a particular way or technique of crossing another entity or obstacle.
-
E.
crossingOf
Indicates that one entity serves as the intersection or crossing point of two or more linear features, such as roads, paths, or tracks.
- 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_69ca82ac7fc081909b1398cf025423af |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3e8eab9c81908098e6b17957316c |
completed | March 31, 2026, 3:25 a.m. |
| PD | Predicate disambiguation | batch_69cb049253d08190bafcecfde493ab8b |
completed | March 30, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69cb14bcbbc0819094a98e7ffffb7a40 |
completed | March 31, 2026, 12:26 a.m. |
Created at: March 30, 2026, 5:20 p.m.