Triple
T178208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Breadsall Priory |
E3621
|
entity |
| Predicate | hasGrounds |
P7001
|
FINISHED |
| Object | extensive landscaped grounds |
—
|
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: extensive landscaped grounds | Statement: [Breadsall Priory, hasGrounds, extensive landscaped grounds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGrounds Context triple: [Breadsall Priory, hasGrounds, extensive landscaped grounds]
-
A.
hasJurisdictionOver
Indicates that one authority or governing body holds legal power or control to make and enforce decisions over another entity, area, or matter.
-
B.
hasSoil
Indicates that one entity possesses, contains, or is associated with a particular type or instance of soil.
-
C.
hasGate
Indicates that one entity possesses, includes, or is equipped with a gate as part of its structure or configuration.
-
D.
hasGroundTransportation
Indicates that an entity provides, includes, or is connected to transportation services or options that operate on land (e.g., cars, buses, trains).
-
E.
previousGround
Indicates that one entity is the immediately preceding ground or surface state relative to another in a sequence or progression.
- F. None of above. chosen
Provenance (4 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_69a25374990081909766d30c79a18e0e |
completed | Feb. 28, 2026, 2:31 a.m. |
| NER | Named-entity recognition | batch_69a258fe7bb08190a56f4a54cadd2fef |
completed | Feb. 28, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69a2566b53d481909c0ed40dd3719e8c |
completed | Feb. 28, 2026, 2:43 a.m. |
| PDg | Predicate description generation | batch_69a2582b7f648190b0ef676b8bdc1c65 |
completed | Feb. 28, 2026, 2:51 a.m. |
Created at: Feb. 28, 2026, 2:39 a.m.