Triple
T12255508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bor |
E292089
|
entity |
| Predicate | hasRiverTransportSignificance |
P165
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Bor, hasRiverTransportSignificance, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRiverTransportSignificance Context triple: [Bor, hasRiverTransportSignificance, true]
-
A.
hasRiver
chosen
Indicates that a location or area contains, is traversed by, or is directly associated with a river.
-
B.
waterwayImportance
Indicates the relative significance or priority of a waterway within a network or region, such as for navigation, transport, or environmental value.
-
C.
hasMajorTownOnRiver
Indicates that a major town is located on and directly associated with a particular river.
-
D.
hasMajorCityOnRiver
Indicates that a major city is located on and directly associated with a particular river.
-
E.
transportsWaterTo
Indicates that one entity carries or conveys water from its location or source to another entity or destination.
- 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_69d6ab67950c8190be08450a06228c4b |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d91d38ee10819093ed41d2954bf4ef |
completed | April 10, 2026, 3:54 p.m. |
| PD | Predicate disambiguation | batch_69d91c46dcd88190a263db30804bff36 |
completed | April 10, 2026, 3:50 p.m. |
Created at: April 8, 2026, 9:52 p.m.