Triple
T18464516
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ringlow |
E451123
|
entity |
| Predicate | situatedBy |
P2409
|
FINISHED |
| Object | upper reaches of the Porter Brook |
—
|
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: upper reaches of the Porter Brook | Statement: [Ringlow, situatedBy, upper reaches of the Porter Brook]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: situatedBy Context triple: [Ringlow, situatedBy, upper reaches of the Porter Brook]
-
A.
locatedIn
Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
-
B.
situatedNextTo
Indicates that one entity is located immediately beside another, with no significant separation between them.
-
C.
situatedAmong
Indicates that an entity is located within or surrounded by multiple other entities in its immediate environment.
-
D.
locatedAlong
chosen
Indicates that one entity is situated adjacent to, or running beside, the length or course of another linear feature (such as a road, river, or railway).
-
E.
isSiteOf
Indicates that a location or place serves as the setting or host for a particular event, activity, or feature.
- 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_69d8d38345688190b565eac2e4cd7935 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e52a82920081909b2b89125db5982a |
completed | April 19, 2026, 7:18 p.m. |
| PD | Predicate disambiguation | batch_69e469d05cf4819099baf1665a9cf18a |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:33 a.m.