Triple
T22238552
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rivers family home |
E549655
|
entity |
| Predicate | nearbyLandscape |
P61270
|
FINISHED |
| Object | bleak moorland |
—
|
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: bleak moorland | Statement: [Rivers family home, nearbyLandscape, bleak moorland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyLandscape Context triple: [Rivers family home, nearbyLandscape, bleak moorland]
-
A.
nearbyLocation
chosen
Indicates that one location is situated close to another location in physical space.
-
B.
nearbyCurrent
Indicates that one entity is located close to another entity at the present moment or in the current context.
-
C.
typicalNearbyLandmarks
Indicates that certain landmarks are commonly found in the vicinity of a given place or location.
-
D.
nearbyElevation
Indicates that one entity is located at or associated with an elevation that is geographically close to the elevation of another entity.
-
E.
nearbyFrontier
Indicates that one entity is located close to a boundary or frontier region associated with another entity.
- 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_69e11e4102b881909cf47d3768e25c19 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f132123a048190ba5a90d7acb9aeb2 |
completed | April 28, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69e71b5177d881908f90abde14ada7dc |
completed | April 21, 2026, 6:38 a.m. |
Created at: April 16, 2026, 8:38 p.m.