Triple
T20656521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Radcot Lock |
E507639
|
entity |
| Predicate | hasWeirLocation |
P25954
|
FINISHED |
| Object | upstream of the lock |
—
|
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: upstream of the lock | Statement: [Radcot Lock, hasWeirLocation, upstream of the lock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWeirLocation Context triple: [Radcot Lock, hasWeirLocation, upstream of the lock]
-
A.
hasWeir
chosen
Indicates the presence of a weir associated with or located at a given entity or site.
-
B.
homeWaterLocation
Indicates the typical body of water or water source associated with an entity’s home or primary habitat.
-
C.
typeOfWeir
Indicates that one entity is a specific kind or classification of weir in relation to another entity.
-
D.
hasNearbyWater
Indicates that one entity is located close to a body of water associated with or relevant to another entity.
-
E.
hasNearbyWaterBoard
Indicates that an entity is located close to, or within the jurisdictional area of, a water management or water regulatory board.
- 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_69e0b4bf58c081908e52a4500e03ff83 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6b2ed48308190b9350a323b9a7952 |
completed | April 20, 2026, 11:12 p.m. |
| PD | Predicate disambiguation | batch_69e5c0315f5081908098707c6455e56e |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 11:43 a.m.