Triple
T5788373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baron Franz von Teuffenbach |
E128327
|
entity |
| Predicate | hasNobilityStatus |
P52082
|
FINISHED |
| Object | titled nobleman |
—
|
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: titled nobleman | Statement: [Baron Franz von Teuffenbach, hasNobilityStatus, titled nobleman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNobilityStatus Context triple: [Baron Franz von Teuffenbach, hasNobilityStatus, titled nobleman]
-
A.
hasNobleStatus
chosen
Indicates that an entity possesses a recognized noble rank, title, or aristocratic status.
-
B.
hasNobilityParticle
Indicates that a person’s name includes a nobility particle (such as “von,” “de,” or “van”) signifying noble or aristocratic status.
-
C.
hasRoyalStatus
Indicates that an entity possesses a recognized royal rank, title, or status within a monarchy or royal system.
-
D.
nobilityClass
Indicates that an entity belongs to, or is associated with, a particular class or rank within a nobility hierarchy.
-
E.
hasHonorificStatus
Indicates that an entity holds or is assigned a particular honorific title, rank, or status 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_69c0084450048190bc647b649a05136b |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02a5297c88190bd28adb2552a26f4 |
completed | March 22, 2026, 5:43 p.m. |
| PD | Predicate disambiguation | batch_69c021d2cd608190b98a7e3aa7001d27 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:51 p.m.