Triple
T17988800
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duke of Rohan-Rohan |
E430311
|
entity |
| Predicate | titleHolderSocialRole |
P108523
|
FINISHED |
| Object | court noble |
—
|
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: court noble | Statement: [Duke of Rohan-Rohan, titleHolderSocialRole, court noble]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleHolderSocialRole Context triple: [Duke of Rohan-Rohan, titleHolderSocialRole, court noble]
-
A.
titleHolderSocialStatus
chosen
Indicates the social rank or class associated with the holder of a particular title within a given context.
-
B.
titleOrRole
Indicates that one entity serves as the title, position, or role held or described by another entity.
-
C.
namedPersonRole
Indicates that a person is identified by name as holding a specific role or position in a given context.
-
D.
titleHolderRelationship
Indicates a relationship where one entity holds, possesses, or bears a specific title in connection to another entity or context.
-
E.
titleHolderProfession
Indicates that the profession or occupation of the entity holding a particular title is the specified value.
- 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_69d8b90364248190a37381adea932f42 |
completed | April 10, 2026, 8:46 a.m. |
| NER | Named-entity recognition | batch_69e4b29d3ad4819096c2600aa2a99f21 |
completed | April 19, 2026, 10:46 a.m. |
| PD | Predicate disambiguation | batch_69e3f90039e4819080527f860dca042e |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:23 a.m.