Triple
T23639637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Midhurst, West Sussex, England |
E583848
|
entity |
| Predicate | nearEstate |
P103472
|
FINISHED |
| Object | Cowdray Estate |
—
|
NE NERFINISHED |
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: Cowdray Estate | Statement: [Midhurst, West Sussex, England, nearEstate, Cowdray Estate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearEstate Context triple: [Midhurst, West Sussex, England, nearEstate, Cowdray Estate]
-
A.
nearbyEstate
chosen
Indicates that one estate is located close to another estate in physical space.
-
B.
realEstate
Indicates a relationship where an entity owns, manages, or is otherwise associated with real property such as land or buildings.
-
C.
realEstateProject
Indicates a relationship where an entity is involved in, associated with, or represents a specific real estate development project.
-
D.
servedNearbyEstates
Indicates that an entity provided services or assistance to estates located in its immediate geographic vicinity.
-
E.
hasNeighbouringEstate
Indicates that one estate is directly adjacent to or shares a boundary with another estate.
- 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_69e248fe1c2c8190ac914d2442ff3d26 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b27fc22c8190abda7398b9fb928c |
completed | April 29, 2026, 7:25 a.m. |
| PD | Predicate disambiguation | batch_69f118d7903c8190bb590a71771e93af |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:48 p.m.