Triple
T8136448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crewe estate |
E189981
|
entity |
| Predicate | isDuchyEstate |
P11791
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Crewe estate, isDuchyEstate, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isDuchyEstate Context triple: [Crewe estate, isDuchyEstate, true]
-
A.
hasEstateType
Indicates that an entity possesses or is associated with a particular category or type of estate.
-
B.
hasAssociatedEstate
Indicates that one entity is linked to, or has responsibility for, a particular estate or property.
-
C.
nobleEstate
chosen
Indicates that an entity is a noble’s estate or property associated with nobility.
-
D.
heirOfEstate
Indicates that one entity is legally designated to inherit the estate or property of another entity, typically upon that entity’s death.
-
E.
hasNearbyHistoricalEstate
Indicates that one entity is located close to another entity that is a recognized historical estate.
- 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.