Triple
T15798288
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heavenly |
E383035
|
entity |
| Predicate | notableLabelScene |
P120059
|
FINISHED |
| Object | Sarah Records roster |
—
|
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: Sarah Records roster | Statement: [Heavenly, notableLabelScene, Sarah Records roster]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableLabelScene Context triple: [Heavenly, notableLabelScene, Sarah Records roster]
-
A.
notableScene
Indicates that a particular scene is especially significant, memorable, or noteworthy within a work or context.
-
B.
sceneLabel
Indicates the categorical label or type assigned to an entire scene based on its overall content or context.
-
C.
notableStage
Indicates that an entity is recognized as an important or distinguished stage or phase in relation to another entity or process.
-
D.
notableDuring
Indicates that something was especially prominent, active, or significant during a particular time period or event.
-
E.
notableStageArea
Indicates that an entity is recognized as a significant or prominent stage or performance area associated with another entity.
- F. None of above. chosen
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_69d86da16e188190b89af699f1ed0bfe |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0b4def80481908f72733ce9133bc6 |
completed | April 16, 2026, 10:07 a.m. |
| PD | Predicate disambiguation | batch_69e00537bd1c81908d6e832792fd934f |
completed | April 15, 2026, 9:37 p.m. |
| PDg | Predicate description generation | batch_69e006b17f7881908b8c7a37f0af4581 |
completed | April 15, 2026, 9:44 p.m. |
Created at: April 10, 2026, 4:48 a.m.