Triple
T36679585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vesdre valley |
E905640
|
entity |
| Predicate | midstreamTown |
P42402
|
FINISHED |
| Object | Verviers |
—
|
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: Verviers | Statement: [Vesdre valley, midstreamTown, Verviers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: midstreamTown Context triple: [Vesdre valley, midstreamTown, Verviers]
-
A.
intermediateTown
Indicates that a town lies along the route between two other locations, serving as an intermediate point on a journey or path.
-
B.
mainTownOn
Indicates that one town is the primary or principal town located on or associated with a particular geographic feature, route, or area.
-
C.
flowsThroughTown
chosen
Indicates that something, typically a river or stream, passes through the area or boundaries of a town.
-
D.
marketTown
Indicates that a town functions as a local commercial center where markets are regularly held for trade and exchange.
-
E.
town
Indicates that a location is classified or functions as a town within a given geographic or administrative context.
- 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_69f76e7011dc819082b324f18b756a1b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7c7be0be88190a480393a2d1ee5bf |
completed | May 3, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69f7c4796ebc819084a0dc08505e5f14 |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 3, 2026, 4:12 p.m.