Triple
T9278374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duke of Castro |
E223004
|
entity |
| Predicate | demesne |
P10159
|
FINISHED |
| Object | Castro and surrounding territory |
—
|
LITERAL 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: Castro and surrounding territory | Statement: [Duke of Castro, demesne, Castro and surrounding territory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: demesne Context triple: [Duke of Castro, demesne, Castro and surrounding territory]
-
A.
domicile
Indicates that one entity serves as the legal or habitual residence or home location of another entity.
-
B.
heldImperialEstate
Indicates that an entity possessed or controlled land or property classified as an imperial estate under a particular imperial authority.
-
C.
domestication
Indicates the process by which humans tame and genetically adapt a wild species over time so it can live and reproduce under human control or in close association with people.
-
D.
feudalCenter
Indicates that a location serves as the primary seat of authority, administration, or power within a feudal system.
-
E.
landholdings
chosen
Indicates the extent or collection of land owned, controlled, or held by an 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_69ca842123588190b3f2e1a69037d141 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd07cb28e081909b2754756c8f5dd0 |
completed | April 1, 2026, 11:55 a.m. |
| PD | Predicate disambiguation | batch_69cc7a576ec88190bbb787eb82e2e539 |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:34 p.m.