Triple
T15721270
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Riding of Yorkshire |
E381097
|
entity |
| Predicate | notableLandscape |
P46334
|
FINISHED |
| Object | 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: moorland | Statement: [North Riding of Yorkshire, notableLandscape, moorland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableLandscape Context triple: [North Riding of Yorkshire, notableLandscape, moorland]
-
A.
notablePark
Indicates that a park is notable or significant in some recognized way, such as historical, cultural, or recreational importance.
-
B.
notableLocationFeature
chosen
Indicates that a location is characterized or distinguished by a particular notable physical or contextual feature.
-
C.
notablePlace
Indicates that a place is especially significant, famous, or noteworthy in relation to the subject.
-
D.
notableValley
Indicates that a valley is recognized as significant or noteworthy, for example due to its geography, history, or cultural importance.
-
E.
notableSite
Indicates that a site holds particular significance, prominence, or recognition in some context.
- 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_69d86d9bf930819082b30cf6d169297c |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e04fb0b51081908e652ec4992296fa |
completed | April 16, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69e00526759c819088b80d85138b8974 |
completed | April 15, 2026, 9:37 p.m. |
Created at: April 10, 2026, 4:45 a.m.