Triple
T34308015
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingston reach of the Thames |
E880363
|
entity |
| Predicate | hasRiversideSettlement |
P55316
|
FINISHED |
| Object | Kingston upon Thames |
—
|
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: Kingston upon Thames | Statement: [Kingston reach of the Thames, hasRiversideSettlement, Kingston upon Thames]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRiversideSettlement Context triple: [Kingston reach of the Thames, hasRiversideSettlement, Kingston upon Thames]
-
A.
hasSettlementOnRiver
Indicates that a settlement is located on or directly adjacent to a specific river.
-
B.
hasRiverBankSettlement
chosen
Indicates that a settlement is located on or directly adjacent to the bank of a river.
-
C.
hasTownOnRiver
Indicates that a town is situated on or directly adjacent to a particular river.
-
D.
isWaterfrontSettlement
Indicates that a settlement is located directly adjacent to a body of water, such as a sea, lake, or river.
-
E.
isUpriverSettlement
Indicates that a settlement is located upriver relative to another point or reference along the same 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_69f349b8bb6c8190ad12a7957a574f04 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fcd867f36081908c88c55a6a1404c1 |
completed | May 7, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f47b188190b4cf4b4c748d9d03 |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 1, 2026, 1:57 a.m.