Triple
T26886235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | City of Cambridge |
E677047
|
entity |
| Predicate | hasRiverValleyFeature |
P40242
|
FINISHED |
| Object | Grand River valley |
—
|
NE NERFINISHED |
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: Grand River valley | Statement: [City of Cambridge, hasRiverValleyFeature, Grand River valley]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRiverValleyFeature Context triple: [City of Cambridge, hasRiverValleyFeature, Grand River valley]
-
A.
hasRiverValleyType
Indicates that an entity (such as a river or geographic area) is characterized by or associated with a specific type of river valley.
-
B.
hasRiverValley
chosen
Indicates that one location contains, includes, or is characterized by a river valley associated with another geographic feature or area.
-
C.
hasIrrigationValley
Indicates that a valley is equipped with or associated with an irrigation system or infrastructure.
-
D.
hasRiver
Indicates that a location or area contains, is traversed by, or is directly associated with a river.
-
E.
hasVillageOnRiver
Indicates that a village is located on or alongside a particular river.
- 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_69eee9bc0c90819085608c8bdc513a57 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f66c5c13808190887180099745673b |
completed | May 2, 2026, 9:27 p.m. |
| PD | Predicate disambiguation | batch_69f66abddc448190a488852f8abdeb2c |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 27, 2026, 5:42 a.m.