Triple
T2635353
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duke of Bronté |
E59731
|
entity |
| Predicate | typeOfFeudalGrant |
P42394
|
FINISHED |
| Object | duchy |
—
|
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: duchy | Statement: [Duke of Bronté, typeOfFeudalGrant, duchy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfFeudalGrant Context triple: [Duke of Bronté, typeOfFeudalGrant, duchy]
-
A.
feudalStatus
Indicates the hierarchical social or legal position an entity holds within a feudal system, such as lord, vassal, or serf.
-
B.
laterFeudalStatus
Indicates that one entity held a particular feudal status or rank at a later time than another entity or than an earlier status.
-
C.
isFeudal
Indicates that one entity holds a feudal relationship to another, typically involving hierarchical obligations such as land tenure, service, or allegiance.
-
D.
typeOfPeerage
Indicates the specific rank or category within a system of peerage that a given title or noble status belongs to.
-
E.
typeOfRight
Indicates the specific category or nature of a right that is held, exercised, or assigned in a given context.
- F. None of above. chosen
Provenance (4 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_69ab4ac8596c8190b34997e73d9e991c |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abd8e085b0819089db4103c0d8cd9b |
completed | March 7, 2026, 7:50 a.m. |
| PD | Predicate disambiguation | batch_69abd812849881908f956845a80e0205 |
completed | March 7, 2026, 7:47 a.m. |
| PDg | Predicate description generation | batch_69abd8abcc348190bfa05c0abc4bcee7 |
completed | March 7, 2026, 7:50 a.m. |
Created at: March 6, 2026, 9:50 p.m.