Triple
T36235120
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dukes of Northumberland |
E891355
|
entity |
| Predicate | ownsHistoricEstate |
P166348
|
FINISHED |
| Object | Alnwick Castle |
—
|
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: Alnwick Castle | Statement: [Dukes of Northumberland, ownsHistoricEstate, Alnwick Castle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ownsHistoricEstate Context triple: [Dukes of Northumberland, ownsHistoricEstate, Alnwick Castle]
-
A.
hasNearbyHistoricalEstate
Indicates that one entity is located close to another entity that is a recognized historical estate.
-
B.
hadEstates
chosen
Indicates that an entity possessed or owned one or more estates (properties or landholdings).
-
C.
hasManorHouse
Indicates that one entity possesses or is associated with a manor house as a property or feature.
-
D.
containsHistoricHouse
Indicates that one entity includes or encompasses a historic house within its boundaries or composition.
-
E.
hasAssociatedEstate
Indicates that one entity is linked to, or has responsibility for, a particular estate or property.
- 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_69f76e4387048190a1b27bcbf4ec7423 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b5a656808190b77b60d4703d0d91 |
completed | May 3, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c44390819084fb5558b354658f |
completed | May 3, 2026, 8:49 p.m. |
Created at: May 3, 2026, 4:09 p.m.