Triple
T9976126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Countess of Angoulême |
E196331
|
entity |
| Predicate | feudalRankWithin |
P66828
|
FINISHED |
| Object | peerage of medieval France |
—
|
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: peerage of medieval France | Statement: [Countess of Angoulême, feudalRankWithin, peerage of medieval France]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: feudalRankWithin Context triple: [Countess of Angoulême, feudalRankWithin, peerage of medieval France]
-
A.
feudalStatus
Indicates the hierarchical social or legal position an entity holds within a feudal system, such as lord, vassal, or serf.
-
B.
nobleRankIn
chosen
Indicates that an entity holds a specified noble rank within a particular political or territorial jurisdiction.
-
C.
nobleRankInHierarchy
Indicates the relative position or level of a noble title within a structured hierarchy of ranks.
-
D.
rankRelativeToPeerage
Indicates how an entity’s hierarchical rank compares to that of a specified peer or peer group within a defined ranking system.
-
E.
feudalType
Indicates the specific kind or category of feudal relationship, structure, or tenure that applies between the related entities.
- 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_69ca82eea2b88190a0e511d21a31f386 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb84b47308190aa2f94fa7320cdc3 |
completed | April 2, 2026, 12:28 a.m. |
| PD | Predicate disambiguation | batch_69cd1d9daa808190b413a1b9a1e929e2 |
completed | April 1, 2026, 1:29 p.m. |
Created at: March 30, 2026, 8:48 p.m.