Triple
T32035347
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Noah |
E818079
|
entity |
| Predicate | realNameInSeries |
P155411
|
FINISHED |
| Object | Hanno Tauber |
—
|
NE NERFINISHED |
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: Hanno Tauber | Statement: [Noah, realNameInSeries, Hanno Tauber]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: realNameInSeries Context triple: [Noah, realNameInSeries, Hanno Tauber]
-
A.
realName
Indicates that one entity is the actual, full, or birth name of another entity, which may be known by an alias, nickname, or alternate identity.
-
B.
titleCharacterRealName
chosen
Indicates that a character known by a title or alias has the specified real (personal) name.
-
C.
fictionalNameInSeries
Indicates that a fictional character is known by a particular name within a specific narrative series or franchise.
-
D.
characterFullName
Indicates that the predicate specifies the complete, formal name of a character.
-
E.
protagonistRealWorldName
Indicates that a character’s name in the real world (outside a fictional, virtual, or alternate setting) is associated with that character as the story’s protagonist.
- 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_69f348fbc8148190b3c0f95d4772b153 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b49b23448190a6c600187b66c7c7 |
completed | May 3, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_69f6b151ad008190836c1bcdec503ce2 |
completed | May 3, 2026, 2:22 a.m. |
Created at: May 1, 2026, 12:18 a.m.