Triple
T8136460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crewe estate |
E189981
|
entity |
| Predicate | landCategory |
P5777
|
FINISHED |
| Object | rural estate |
—
|
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: rural estate | Statement: [Crewe estate, landCategory, rural estate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: landCategory Context triple: [Crewe estate, landCategory, rural estate]
-
A.
realEstateCategory
chosen
Indicates the classification of a property into a specific type or category within real estate (e.g., residential, commercial, industrial).
-
B.
landPolicy
Indicates a relationship where an authority defines or applies rules governing the ownership, use, management, or distribution of land.
-
C.
land
Indicates coming down from the air or a higher position to make contact with and settle on a surface.
-
D.
traditionalLandIncludes
Indicates that a specified traditional land area encompasses or contains another geographic area within its recognized boundaries.
-
E.
landUseIncludes
Indicates that a specified land area contains or permits the specified type(s) of land use within its boundaries.
- 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_69ca82bd9900819099477cdc2eb4244f |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb440171d48190afa4a312ab19389c |
completed | March 31, 2026, 3:48 a.m. |
| PD | Predicate disambiguation | batch_69cb369c0d0481908762c488d7f77e74 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:35 p.m.