Triple
T28826160
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lady Denham |
E727909
|
entity |
| Predicate | controlsPropertyIn |
P105713
|
FINISHED |
| Object | Sanditon 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: Sanditon estate | Statement: [Lady Denham, controlsPropertyIn, Sanditon estate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controlsPropertyIn Context triple: [Lady Denham, controlsPropertyIn, Sanditon estate]
-
A.
controlledIn
chosen
Indicates that one entity exercised control, authority, or governance over another entity within a specific context or domain.
-
B.
controlsWith
Indicates that one entity exercises authority, direction, or regulatory power over another entity through specific means or mechanisms.
-
C.
controlsOrControlled
Indicates that one entity has control over another entity or is itself under the control of that other entity.
-
D.
controlledFor
Indicates that the influence or effect of a specified factor has been accounted for or neutralized when assessing the relationship between other variables or entities.
-
E.
controlFrom
Indicates that one entity exercises authority, influence, or regulatory power over another entity or process.
- 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_69f0319d09088190bbf14cdf1987792a |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69fb563aec448190875410fb1a3ed624 |
completed | May 6, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69fb35b9ede881908aaae93a215525df |
completed | May 6, 2026, 12:36 p.m. |
Created at: April 28, 2026, 6:36 a.m.