Triple
T38058747
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kirklees Valley Local Nature Reserve |
E950275
|
entity |
| Predicate | hasPastLandUse |
P44099
|
FINISHED |
| Object | industrial site |
—
|
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: industrial site | Statement: [Kirklees Valley Local Nature Reserve, hasPastLandUse, industrial site]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPastLandUse Context triple: [Kirklees Valley Local Nature Reserve, hasPastLandUse, industrial site]
-
A.
formerLandUse
chosen
Indicates the type of land use that characterized a location prior to its current or present use.
-
B.
hasHistoricalLandCover
Indicates that an entity is associated with information about the land cover that existed in a specified area during a past time period.
-
C.
hasLandUseCharacter
Indicates that one entity possesses or is associated with a particular type or pattern of land use.
-
D.
hasLandUseTrend
Indicates a relationship where an entity exhibits a particular pattern or change over time in how its land is used.
-
E.
landUseChangeTo
Indicates a transition in how a piece of land is used, from its previous use to a new designated use.
- 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_69f76f01e63c819093b6012fc974f35a |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a007241df8081909dbad651fda82aa7 |
completed | May 10, 2026, 11:55 a.m. |
| PD | Predicate disambiguation | batch_6a0071e77ed081908cd618da8977d878 |
completed | May 10, 2026, 11:54 a.m. |
Created at: May 3, 2026, 4:21 p.m.