Triple
T5788381
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baron Franz von Teuffenbach |
E128327
|
entity |
| Predicate | hasFictionalUniverseAspect |
P15645
|
FINISHED |
| Object | 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: nobility | Statement: [Baron Franz von Teuffenbach, hasFictionalUniverseAspect, nobility]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFictionalUniverseAspect Context triple: [Baron Franz von Teuffenbach, hasFictionalUniverseAspect, nobility]
-
A.
hasFictionalUniverseElement
chosen
Indicates that one entity is a component, feature, or constituent part of the fictional universe represented by the other entity.
-
B.
hasFictionalUniverseGenre
Indicates that a fictional universe is associated with a particular genre that characterizes its overall style, themes, or narrative type.
-
C.
portraysFictionalUniverse
Indicates that one entity depicts, represents, or presents the fictional universe in which another entity is set.
-
D.
fictionalUniverse
Indicates that two entities exist within, or are associated with, the same fictional universe or narrative setting.
-
E.
hasFictionalUniverseConflict
Indicates that there is a conflict or incompatibility between the fictional universes associated with the related entities.
- 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.