Triple
T24612329
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Appleton Roebuck |
E609151
|
entity |
| Predicate | hasCountryHouseNearby |
P97839
|
FINISHED |
| Object | Nun Appleton Hall |
—
|
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: Nun Appleton Hall | Statement: [Appleton Roebuck, hasCountryHouseNearby, Nun Appleton Hall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCountryHouseNearby Context triple: [Appleton Roebuck, hasCountryHouseNearby, Nun Appleton Hall]
-
A.
hasCountryHouse
chosen
Indicates that one entity possesses or owns a house located in the countryside.
-
B.
hasHouseWithin
Indicates that one entity possesses or is associated with a house that is located within the spatial or administrative boundaries of another entity.
-
C.
hasNearbyHotel
Indicates that one entity is located close to or within a short distance of a hotel.
-
D.
hasMainBuildingNear
Indicates that the primary or central building associated with an entity is located in close physical proximity to another specified entity or place.
-
E.
hasNeighbourhood
Indicates that one entity is located within, or is associated with, a particular neighborhood area of another entity.
- 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_69e2c4d1140081909c58667bf68f80c3 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f2be044d4c819094e14eda28d371a7 |
completed | April 30, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f2a6ca751c8190a040c10d701ecf3a |
completed | April 30, 2026, 12:48 a.m. |
Created at: April 18, 2026, 2:31 a.m.