Triple
T13457426
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | de Beaumont |
E311269
|
entity |
| Predicate | associatedWithSocialStatus |
P45754
|
FINISHED |
| Object | hereditary nobility |
—
|
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: hereditary nobility | Statement: [de Beaumont, associatedWithSocialStatus, hereditary nobility]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithSocialStatus Context triple: [de Beaumont, associatedWithSocialStatus, hereditary nobility]
-
A.
associatedWithSocialImage
Indicates a relationship where something is linked or connected to a particular social image, reputation, or public perception.
-
B.
associatedStatus
chosen
Indicates that one entity is linked to or characterized by a particular status or condition.
-
C.
associationStatus
Indicates the current state or condition of an established association or relationship between entities.
-
D.
associatedPeopleStatus
Indicates the role, condition, or standing of people who are connected or linked to a given entity or event.
-
E.
socialMediaPlatformAssociatedWith
Indicates that there is an association or linkage between an entity and a specific social media platform.
- 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_69d806a938b8819097ec43a2229fc7f9 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaf0a75008190a508060c85f73604 |
completed | April 12, 2026, 2:41 p.m. |
| PD | Predicate disambiguation | batch_69d9a03ce03481908c61094f0cc0c158 |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:41 p.m.