Triple
T37475019
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Minchinhampton Old Course |
E931254
|
entity |
| Predicate | isOnCommonLand |
P41739
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Minchinhampton Old Course, isOnCommonLand, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOnCommonLand Context triple: [Minchinhampton Old Course, isOnCommonLand, yes]
-
A.
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.
-
B.
hasNearbyPublicLand
Indicates that one entity is located close to an area of public land, such as parks, reserves, or other publicly accessible open spaces.
-
C.
ownedLandBy
Indicates that one entity possesses legal or recognized ownership rights over a piece or area of land associated with another entity.
-
D.
hasLandStatus
chosen
Indicates that an entity possesses a particular legal or administrative status regarding land (such as ownership, tenure, protection, or use designation).
-
E.
ownsLandFor
Indicates that one entity possesses or holds ownership rights to land for the benefit, use, or purpose of 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_69f76ec2af148190897d101070d7f415 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb8e652328819082cff21f5a1fe709 |
completed | May 6, 2026, 6:54 p.m. |
| PD | Predicate disambiguation | batch_69fb8d0c53c08190b64291bac58cdb4c |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:17 p.m.