Triple
T25462502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tosson Hill |
E638086
|
entity |
| Predicate | accessLandStatus |
P32027
|
FINISHED |
| Object | open access 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: open access land | Statement: [Tosson Hill, accessLandStatus, open access land]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accessLandStatus Context triple: [Tosson Hill, accessLandStatus, open access land]
-
A.
hasLandStatus
Indicates that an entity possesses a particular legal or administrative status regarding land (such as ownership, tenure, protection, or use designation).
-
B.
accessLandIncludes
Indicates that one land access area or right encompasses or contains another within its scope.
-
C.
accessStatus
chosen
Indicates the current level or state of permission or availability for accessing a resource or entity.
-
D.
isPublicLand
Indicates that a given area of land is owned or managed by a government or public authority and is accessible or designated for use by the general public.
-
E.
landerStatus
Indicates the current operational or situational state of a lander in its mission lifecycle.
- 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_69e75db8bab08190baca80b4a8c315fd |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f606c79ad081908369605f72e65ca6 |
completed | May 2, 2026, 2:14 p.m. |
| PD | Predicate disambiguation | batch_69f602ce79ec8190b8336c2b9de18ac7 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 21, 2026, 2:12 p.m.