Triple
T26114423
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Psych-O's |
E658781
|
entity |
| Predicate | formedAroundShowPremiere |
P180923
|
FINISHED |
| Object | Psych season 1 |
—
|
NE NERFINISHED |
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: Psych season 1 | Statement: [Psych-O's, formedAroundShowPremiere, Psych season 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formedAroundShowPremiere Context triple: [Psych-O's, formedAroundShowPremiere, Psych season 1]
-
A.
composerPresentAtPremiere
Indicates that the composer of a work was physically present at the premiere performance of that work.
-
B.
conductedPremiereOf
Indicates that one entity organized and presented the first public performance or showing of another entity (such as a work, event, or production).
-
C.
premieredWith
Indicates that one entity made its first public debut or initial showing together with another entity, at the same time or in the same event.
-
D.
premieredIn
Indicates that a creative work first publicly debuted or was initially presented in a particular place, event, or context.
-
E.
premieredOn
Indicates that an event, work, or production had its first public showing or debut on a specified date or at a specified time.
- 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_69ee5bc20298819099a42be042eb2349 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f75dc25fa08190b371faf36d9fb72c |
completed | May 3, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f758586534819083e91172f4bf5098 |
completed | May 3, 2026, 2:14 p.m. |
| PDg | Predicate description generation | batch_69f75dc140c4819085063d6c4c36ca61 |
completed | May 3, 2026, 2:37 p.m. |
Created at: April 26, 2026, 8:04 p.m.