Triple
T31043434
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Erdmuthe |
E791057
|
entity |
| Predicate | nameBearerNobilityTitle |
P83908
|
FINISHED |
| Object | princess |
—
|
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: princess | Statement: [Erdmuthe, nameBearerNobilityTitle, princess]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nameBearerNobilityTitle Context triple: [Erdmuthe, nameBearerNobilityTitle, princess]
-
A.
nameBearerHonor
Indicates that an entity bears or carries a name as an honor or mark of respect bestowed by another entity.
-
B.
nobilityTitleType
Indicates the specific kind or category of noble rank or title associated with an entity.
-
C.
nobleTitleOrStatus
Indicates that one entity holds, claims, or is associated with a particular noble rank, title, or social status in relation to another entity.
-
D.
nameBearerType
chosen
Indicates the specific role or capacity in which an entity bears or carries a given name (e.g., as a person, place, organization, or other type of name bearer).
-
E.
recognizedHeirTitle
Indicates that an individual is formally acknowledged as the legitimate holder or successor of a specific hereditary 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_69f224ca2fa881908a3ac5fedf207b90 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f694fb85f881909734cf13cea84c78 |
completed | May 3, 2026, 12:21 a.m. |
| PD | Predicate disambiguation | batch_69f690f13d7481908ddfefe95df2a1c2 |
completed | May 3, 2026, 12:04 a.m. |
Created at: April 29, 2026, 8:59 p.m.