Triple
T27118890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Biggleswade Common |
E686932
|
entity |
| Predicate | hasRightOfCommon |
P39434
|
FINISHED |
| Object | grazing rights |
—
|
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: grazing rights | Statement: [Biggleswade Common, hasRightOfCommon, grazing rights]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRightOfCommon Context triple: [Biggleswade Common, hasRightOfCommon, grazing rights]
-
A.
hasRightsOver
chosen
Indicates that one entity possesses legal, moral, or formal entitlements or authority over another entity.
-
B.
hasRightsSimilarTo
Indicates that one entity possesses rights that are comparable or equivalent in scope or nature to those held by another entity.
-
C.
hasLegalRight
Indicates that an entity possesses an officially recognized legal entitlement or permission to perform an action or hold a claim regarding another entity.
-
D.
coversRight
Indicates that one entity extends over, protects, or conceals the right side of another entity.
-
E.
hasRightRecognizedIn
Indicates that an entity’s right is formally acknowledged or upheld within a specified context, system, or jurisdiction.
- 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_69ef148c2b588190afc15b529f7af845 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f67c9fe7b48190b79b4041357edb49 |
completed | May 2, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69f678cc272081909e5c70f1bc7407f0 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 27, 2026, 8:58 a.m.