Triple
T33815901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Head in the Clouds (reprise) |
E866672
|
entity |
| Predicate | isRecurringSegment |
P58011
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Head in the Clouds (reprise), isRecurringSegment, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRecurringSegment Context triple: [Head in the Clouds (reprise), isRecurringSegment, true]
-
A.
recurringSegmentOn
chosen
Indicates that one entity appears repeatedly as a regular segment or feature within another entity, such as a show, publication, or series.
-
B.
hasRecurringElement
Indicates that an entity includes an element that appears repeatedly or occurs multiple times within it.
-
C.
recurringDuring
Indicates that an event or state happens repeatedly within the time span or context defined by another event or interval.
-
D.
recurringSeries
Indicates that an event, action, or pattern occurs repeatedly over time as part of an ongoing series rather than as a one-time instance.
-
E.
appearsInSegmentOf
Indicates that one entity occurs within, or is featured as part of, a specific segment or subsection of 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_69f349911a8c81908478662194b23d8c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7051ad6e4819095e82bbd64761803 |
completed | May 3, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69f700fe24e08190998e2c96fbaaad38 |
completed | May 3, 2026, 8:02 a.m. |
Created at: May 1, 2026, 1:46 a.m.