Triple
T32074856
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Act III of Swan Lake |
E819114
|
entity |
| Predicate | isTurningPointForCharacter |
P93589
|
FINISHED |
| Object | Prince Siegfried |
—
|
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: Prince Siegfried | Statement: [Act III of Swan Lake, isTurningPointForCharacter, Prince Siegfried]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTurningPointForCharacter Context triple: [Act III of Swan Lake, isTurningPointForCharacter, Prince Siegfried]
-
A.
isPivotalForCharacter
chosen
Indicates that something plays a crucial, defining role in shaping a character’s development, decisions, or narrative arc.
-
B.
trackCharacter
Indicates that one entity follows, monitors, or keeps a record of another entity’s actions, state, or progression over time.
-
C.
isScoreForCharacter
Indicates that a given score value is associated with, or belongs to, a particular character.
-
D.
isRecurringCharacter
Indicates that an entity appears repeatedly or regularly within a given narrative, series, or context rather than only once.
-
E.
basedOnCharacterBy
Indicates that one work, adaptation, or portrayal is derived from or inspired by a character created 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_69f348ff8ef88190931c08ba530a36bc |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b52ac6f48190ac3e563e45464d43 |
completed | May 3, 2026, 2:38 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a7bdb481908d16a32f49e38c2c |
completed | May 3, 2026, 2:32 a.m. |
Created at: May 1, 2026, 12:23 a.m.