Triple
T20854409
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Estate of the Nobility |
E513442
|
entity |
| Predicate | privilegedEstate |
P11791
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Estate of the Nobility, privilegedEstate, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: privilegedEstate Context triple: [Estate of the Nobility, privilegedEstate, yes]
-
A.
improvedEstate
Indicates that an estate has undergone enhancements, developments, or upgrades that increase its value or utility.
-
B.
nobleEstate
chosen
Indicates that an entity is a noble’s estate or property associated with nobility.
-
C.
heirOfEstate
Indicates that one entity is legally designated to inherit the estate or property of another entity, typically upon that entity’s death.
-
D.
nobleEstateDominance
Indicates a relationship where one noble estate holds controlling power, influence, or authority over another estate or over the surrounding lands.
-
E.
hadEstate
Indicates that an entity possessed or owned a particular estate or landed 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_69e0b4f5b01081909452f654d2fc3f50 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c3a7113c819087994bcdfe643bc1 |
completed | April 21, 2026, 12:24 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a593f481908beb457c29f1ce73 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:44 p.m.