Triple
T33174767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flon River |
E849136
|
entity |
| Predicate | coveredSection |
P187400
|
FINISHED |
| Object | flows underground through much of central Lausanne |
—
|
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: flows underground through much of central Lausanne | Statement: [Flon River, coveredSection, flows underground through much of central Lausanne]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coveredSection Context triple: [Flon River, coveredSection, flows underground through much of central Lausanne]
-
A.
coveredSectionsLocation
Indicates the specific location or area where the covered sections are situated or applied.
-
B.
coversSection
Indicates that one entity includes, addresses, or provides content for a particular section of another entity.
-
C.
coveredSector
Indicates that one entity provides coverage, service, or operational responsibility for a particular sector or area.
-
D.
linedSections
Indicates that one section is arranged or positioned in alignment with another section.
-
E.
sectionProvided
Indicates that a specific section or portion of content has been supplied or made available by one entity to another.
- 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_69f3495d06508190b0b7729982982cea |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fb563aec448190875410fb1a3ed624 |
completed | May 6, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69fb35b9ede881908aaae93a215525df |
completed | May 6, 2026, 12:36 p.m. |
| PDg | Predicate description generation | batch_69fb563a28d88190b28345c465c545f8 |
completed | May 6, 2026, 2:54 p.m. |
Created at: May 1, 2026, 1:29 a.m.