Triple
T25326615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | River Cher |
E635032
|
entity |
| Predicate | notableLandmarkOnBanks |
P8340
|
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, notableLandmarkOnBanks, Château de Chenonceau]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableLandmarkOnBanks Context triple: [River Cher, notableLandmarkOnBanks, Château de Chenonceau]
-
A.
hasLandmarkOnBank
chosen
Indicates that a landmark is located on the bank (shore or edge) of a geographic feature such as a river, lake, or canal.
-
B.
notableSiteAssociatedWith
Indicates that there is a significant or noteworthy site or location that is associated with, related to, or prominently linked to the given entity.
-
C.
hasCityOnBank
Indicates that a city is located on the bank of a particular river or body of water.
-
D.
notablePlace
Indicates that a place is especially significant, famous, or noteworthy in relation to the subject.
-
E.
cityOnBothBanks
Indicates that a city is situated so that it occupies or extends across both banks of a 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_69e75a9908108190a95427a97020632a |
completed | April 21, 2026, 11:08 a.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. |
Created at: April 21, 2026, 1:30 p.m.