Triple
T8136445
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crewe estate |
E189981
|
entity |
| Predicate | hasHereditaryOwner |
P6021
|
FINISHED |
| Object | monarch of the United Kingdom |
—
|
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: monarch of the United Kingdom | Statement: [Crewe estate, hasHereditaryOwner, monarch of the United Kingdom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHereditaryOwner Context triple: [Crewe estate, hasHereditaryOwner, monarch of the United Kingdom]
-
A.
hasHereditaryChief
Indicates that an entity is led or governed by a chief whose position is inherited through family lineage.
-
B.
hasTypeOfHeritage
Indicates that an entity is associated with a specific category or classification of heritage (such as cultural, natural, or historical heritage).
-
C.
hasHereditaryOffice
chosen
Indicates that an entity holds an office or position that is passed down through family lineage rather than acquired by election, appointment, or merit.
-
D.
hasPetOwner
Indicates that a person or entity serves as the owner or caretaker of a particular pet.
-
E.
hasFamilyNameOfOwner
Indicates that an entity has an owner whose family (last) name is the specified value.
- 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_69ca82bd9900819099477cdc2eb4244f |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb440171d48190afa4a312ab19389c |
completed | March 31, 2026, 3:48 a.m. |
| PD | Predicate disambiguation | batch_69cb369c0d0481908762c488d7f77e74 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:35 p.m.