Triple
T11094712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Jewel of Seven Stars |
E262346
|
entity |
| Predicate | originalEnding |
P40273
|
FINISHED |
| Object | 1903 tragic ending |
—
|
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: 1903 tragic ending | Statement: [The Jewel of Seven Stars, originalEnding, 1903 tragic ending]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalEnding Context triple: [The Jewel of Seven Stars, originalEnding, 1903 tragic ending]
-
A.
alternateEnding
Indicates that one version of a work provides a different conclusion or final sequence of events compared to the original or primary ending.
-
B.
originalFinale
chosen
Indicates that something serves as the initial or authentic concluding part or ending of another work, event, or sequence.
-
C.
notableEnding
Indicates that an entity concludes or finishes in a way that is remarkable, memorable, or otherwise noteworthy.
-
D.
endedWith
Indicates that one event, process, or state concluded with or was finalized by another specified event, condition, or outcome.
-
E.
hasUnfinishedEnding
Indicates that an entity concludes in an incomplete, unresolved, or open-ended manner rather than reaching a fully finished state.
- 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_69d6aa9a40d88190a373e2c7e48285db |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d79a0783e88190aae3d461730c2d70 |
completed | April 9, 2026, 12:22 p.m. |
| PD | Predicate disambiguation | batch_69d744185a5881909ba4cf151d1798ec |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:27 p.m.