Triple
T37707872
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earldom of Richmond |
E939240
|
entity |
| Predicate | hadFeudalConnectionsTo |
P7255
|
FINISHED |
| Object | Duke of Brittany |
—
|
NE NERFINISHED |
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: Duke of Brittany | Statement: [Earldom of Richmond, hadFeudalConnectionsTo, Duke of Brittany]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadFeudalConnectionsTo Context triple: [Earldom of Richmond, hadFeudalConnectionsTo, Duke of Brittany]
-
A.
historicalRelationship
Indicates a relationship that existed between entities in the past, often tied to a specific historical period, context, or event.
-
B.
countryOfDynasticConnection
Indicates that there exists a historical dynastic link—such as through ruling families, royal marriages, or shared dynasties—between the subject and the referenced country.
-
C.
vassalsOf
chosen
Indicates that one entity serves as a subordinate or dependent vassal under the authority or suzerainty of another entity.
-
D.
hasDynasticConnections
Indicates that one entity is related to another through familial or hereditary ties between ruling or noble dynasties.
-
E.
laterPeerageConnections
Indicates that one entity acquires or forms peerage-related ties (such as titles, ranks, or noble associations) at a later time or stage in relation to another entity.
- 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_69f76edb49dc8190b951dce9ce6ef789 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbb9e8108c8190ae1c7940b1677e95 |
completed | May 6, 2026, 10 p.m. |
| PD | Predicate disambiguation | batch_69fbb141605c8190b9c27d70352522db |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:18 p.m.