Triple
T35398725
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Countess of Poitiers |
E1023158
|
entity |
| Predicate | feudalRankRelative |
P80950
|
FINISHED |
| Object | below duchess |
—
|
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: below duchess | Statement: [Countess of Poitiers, feudalRankRelative, below duchess]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: feudalRankRelative Context triple: [Countess of Poitiers, feudalRankRelative, below duchess]
-
A.
feudalStatus
Indicates the hierarchical social or legal position an entity holds within a feudal system, such as lord, vassal, or serf.
-
B.
rankRelativeToPeerage
Indicates how an entity’s hierarchical rank compares to that of a specified peer or peer group within a defined ranking system.
-
C.
ecclesiasticalRankRelative
Indicates a hierarchical relationship between two ecclesiastical positions, specifying which rank is higher, lower, or otherwise ordered relative to the other within a church structure.
-
D.
nobleRankInHierarchy
chosen
Indicates the relative position or level of a noble title within a structured hierarchy of ranks.
-
E.
associatedNobleRank
Indicates that an entity is linked to or holds a particular noble rank or title.
- 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_69f76df43ca4819098711ca4370f1bb9 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7953827b48190aec5b07f65a3b304 |
completed | May 3, 2026, 6:34 p.m. |
| PD | Predicate disambiguation | batch_69f7910770108190bdd39ddb5d304f54 |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 3, 2026, 4:03 p.m.