Triple
T29029024
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Robert Schumann |
E737674
|
entity |
| Predicate | usedPersonae |
P70717
|
FINISHED |
| Object | Florestan |
—
|
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: Florestan | Statement: [Robert Schumann, usedPersonae, Florestan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedPersonae Context triple: [Robert Schumann, usedPersonae, Florestan]
-
A.
helpedDefinePersonaOf
Indicates that one entity significantly contributed to shaping or establishing the persona, image, or character of another entity.
-
B.
basedOnPersona
Indicates that something is created, customized, or decided according to a specific persona’s characteristics, preferences, or profile.
-
C.
stagePersonaOf
chosen
Indicates a relationship where one entity is the staged or performed persona, role, or character representation of another entity.
-
D.
primaryPersona
Indicates that one entity is the main or most representative persona associated with another entity, distinguishing it from any secondary or supporting personas.
-
E.
characterPersona
Indicates that one entity embodies, represents, or assumes the persona, role, or character identity specified by 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_69f077ef00fc81909325f084ad37c035 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6691f5e188190b12c7b2eb729a45e |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f6659b62fc8190b21555d0ba54db2d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 9:54 a.m.