Triple
T33120803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iver |
E847589
|
entity |
| Predicate | hasCountryHouseEstateNearby |
P103472
|
FINISHED |
| Object | Black Park |
E1703217
|
NE 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: Black Park | Statement: [Iver, hasCountryHouseEstateNearby, Black Park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCountryHouseEstateNearby Context triple: [Iver, hasCountryHouseEstateNearby, Black Park]
-
A.
hasNearbyHistoricalEstate
Indicates that one entity is located close to another entity that is a recognized historical estate.
-
B.
hasNeighbouringEstate
Indicates that one estate is directly adjacent to or shares a boundary with another estate.
-
C.
countryHouseOnEstate
Indicates that a country house is located on, and forms part of, a particular estate.
-
D.
nearbyEstate
chosen
Indicates that one estate is located close to another estate in physical space.
-
E.
hasNotableHousingEstate
Indicates that a place or area contains a housing estate that is considered significant or noteworthy in some recognized way.
- F. None of above.
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_69f3495751a081909850af5843da40dc |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a34f03c0b9c81909420d6f21becc9f0 |
completed | June 19, 2026, 7:31 a.m. |
| PD | Predicate disambiguation | batch_6a0379f338b881908e5593e45d764f4d |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:27 a.m.