Triple
T30311018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | E lucevan le stelle |
E770922
|
entity |
| Predicate | characterStatusInScene |
P129147
|
FINISHED |
| Object | awaiting execution |
—
|
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: awaiting execution | Statement: [E lucevan le stelle, characterStatusInScene, awaiting execution]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: characterStatusInScene Context triple: [E lucevan le stelle, characterStatusInScene, awaiting execution]
-
A.
characterStatusInStory
Indicates the role or condition a character holds within the context of a specific story or narrative.
-
B.
roleInScene
Indicates that an entity participates in a particular scene with a specific role or function within that scene.
-
C.
leadCharacterStatus
Indicates the role or condition of an entity when it serves as the primary or central character in a narrative or context.
-
D.
featuresCharacterWithStatus
chosen
Indicates that something (such as a work or scene) includes a character who has a specified status or condition.
-
E.
isCharacterInSetting
Indicates that a particular character appears or exists within a specified setting or environment.
- 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_69f22488f224819081b0f3ec41ab975c |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fddf721c1481909301a0f379368f10 |
completed | May 8, 2026, 1:04 p.m. |
| PD | Predicate disambiguation | batch_69fddda1ae7c8190b5848ff9a9e39826 |
completed | May 8, 2026, 12:57 p.m. |
Created at: April 29, 2026, 7:50 p.m.