Triple
T25326603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Cher |
E635032
|
entity |
| Predicate | flowsBeneath |
P45083
|
FINISHED |
| Object | Château de Chenonceau |
—
|
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: Château de Chenonceau | Statement: [River Cher, flowsBeneath, Château de Chenonceau]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flowsBeneath Context triple: [River Cher, flowsBeneath, Château de Chenonceau]
-
A.
flowsBelow
Indicates that one entity moves or passes in a downward direction relative to another, positioned at a lower level or beneath it.
-
B.
flowsBeside
Indicates that one entity moves or runs alongside another entity in close proximity without crossing or intersecting it.
-
C.
flowsAt
Indicates that a fluid or substance moves through or along a specific location, point, or region.
-
D.
flowsAround
Indicates that one entity moves in a continuous, typically fluid motion encircling or passing on multiple sides around another entity.
-
E.
flowsUnder
chosen
Indicates that one entity (typically a river, stream, or liquid) passes beneath another entity (such as a bridge, structure, or obstacle) along its course.
- 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_69e75a9908108190a95427a97020632a |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f497bf12e081908b8c0f523586fca3 |
completed | May 1, 2026, 12:08 p.m. |
| PD | Predicate disambiguation | batch_69f45d06d0388190b36ecde92013624a |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 21, 2026, 1:30 p.m.