Triple
T9846386
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cléo from 5 to 7 |
E239350
|
entity |
| Predicate | openingSequenceFormat |
P90337
|
FINISHED |
| Object | color |
—
|
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: color | Statement: [Cléo from 5 to 7, openingSequenceFormat, color]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openingSequenceFormat Context triple: [Cléo from 5 to 7, openingSequenceFormat, color]
-
A.
openingSequenceType
Indicates the specific kind or category of an opening sequence associated with an entity or event.
-
B.
openingStage
Indicates the initial phase or first part of a process, event, or sequence in which subsequent stages will follow.
-
C.
openingMotif
Indicates that one element serves as the initial recurring theme or pattern that introduces and sets the tone for another element, such as a work or sequence.
-
D.
openingInvocation
Indicates the act of formally beginning an event, process, or sequence through an initiating statement, action, or call.
-
E.
openingLine
Indicates that one entity is the first line or initial statement that begins another entity, such as a text, speech, or conversation.
- 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_69ca84e3f0c48190ada72a65ebd50efd |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb36156308190b26892702f3b41e0 |
completed | April 2, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69cd03e57cac8190914bb5ae608a6e0e |
completed | April 1, 2026, 11:39 a.m. |
| PDg | Predicate description generation | batch_69cd06ace53081909b5f81f382f6591e |
completed | April 1, 2026, 11:51 a.m. |
Created at: March 30, 2026, 8:34 p.m.