Triple
T10551421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Incredible Edible Todmorden |
E248955
|
entity |
| Predicate | usesLandType |
P43475
|
FINISHED |
| Object | public land |
—
|
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: public land | Statement: [Incredible Edible Todmorden, usesLandType, public land]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesLandType Context triple: [Incredible Edible Todmorden, usesLandType, public land]
-
A.
usesOnLand
Indicates that one entity employs or operates another entity specifically in a land-based context.
-
B.
hasLandUseCharacter
chosen
Indicates that one entity possesses or is associated with a particular type or pattern of land use.
-
C.
hasLandComponent
Indicates that something includes, consists of, or is associated with a land-based part or portion as one of its components.
-
D.
landUseIncludes
Indicates that a specified land area contains or permits the specified type(s) of land use within its boundaries.
-
E.
hasLandStatus
Indicates that an entity possesses a particular legal or administrative status regarding land (such as ownership, tenure, protection, or use designation).
- 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_69d381c733c08190ab1dd6239f5f34ae |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d52710869c81909b6db1a190825bad |
completed | April 7, 2026, 3:47 p.m. |
| PD | Predicate disambiguation | batch_69d518fa0b4081909bffc936d78bd77b |
completed | April 7, 2026, 2:47 p.m. |
Created at: April 6, 2026, 12:34 p.m.