Triple
T29026476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fantasy Pieces |
E737605
|
entity |
| Predicate | associatedPersonas |
P86543
|
FINISHED |
| Object | Florestan |
E736544
|
NE 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: Florestan | Statement: [Fantasy Pieces, associatedPersonas, Florestan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedPersonas Context triple: [Fantasy Pieces, associatedPersonas, Florestan]
-
A.
associatedPerformerPersona
chosen
Indicates a relationship where a performer is linked to a specific persona or role identity they adopt in their performances.
-
B.
associatedWithPersonaTrait
Indicates that an entity is linked to or characterized by a particular persona trait or attribute.
-
C.
stagePersonaOf
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.
basedOnPersona
Indicates that something is created, customized, or decided according to a specific persona’s characteristics, preferences, or profile.
- F. None of above.
Provenance (4 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_6a02fb5ca96081908ff618f560011940 |
completed | May 12, 2026, 10:05 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a25699fc0808190b6925faef5d32c18 |
completed | June 7, 2026, 12:52 p.m. |
| PD | Predicate disambiguation | batch_6a02f9602b308190a97f81821e12b13f |
completed | May 12, 2026, 9:56 a.m. |
Created at: April 28, 2026, 9:53 a.m.