Triple
T3899547
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earl of Kildare |
E90450
|
entity |
| Predicate | originalSocialClass |
P26434
|
FINISHED |
| Object | Anglo-Norman aristocracy |
—
|
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: Anglo-Norman aristocracy | Statement: [Earl of Kildare, originalSocialClass, Anglo-Norman aristocracy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalSocialClass Context triple: [Earl of Kildare, originalSocialClass, Anglo-Norman aristocracy]
-
A.
socialClassAtBirth
chosen
Indicates the social class or socioeconomic status into which an individual was born.
-
B.
dominantSocialClass
Indicates that one social class holds primary power, influence, or status over others within a given social structure or context.
-
C.
traditionalSocialClass
Indicates that an entity belongs to or is associated with a particular traditional social class within a social hierarchy.
-
D.
socialClassSystem
Indicates a hierarchical organization of people into social classes based on status, power, or economic position.
-
E.
associatedWithSocialClass
Indicates a relationship in which an entity is linked or connected to a particular social class or socioeconomic stratum.
- 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_69aed95d315881908cbf1bf4a7215fbf |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef1abe2dc81909c18aeae9b286898 |
completed | March 9, 2026, 4:13 p.m. |
| PD | Predicate disambiguation | batch_69aee75b5b808190a348a31b1325d3d0 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:21 p.m.