Triple
T32877133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vulcan fight theme |
E840957
|
entity |
| Predicate | franchiseDebutSeries |
P63817
|
FINISHED |
| Object | Star Trek: The Original Series |
—
|
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: Star Trek: The Original Series | Statement: [Vulcan fight theme, franchiseDebutSeries, Star Trek: The Original Series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: franchiseDebutSeries Context triple: [Vulcan fight theme, franchiseDebutSeries, Star Trek: The Original Series]
-
A.
franchiseDebut
chosen
Indicates the first appearance or introduction of an entity within a particular franchise or series.
-
B.
franchiseStartSeason
Indicates the season in which a particular franchise or series first began or was introduced.
-
C.
franchiseStart
Indicates the point in time or event at which a franchise or franchising relationship is initiated or begins.
-
D.
franchiseDebutScore
Indicates the score or rating achieved by an entity in its first appearance within a particular franchise.
-
E.
beganWithFranchise
Indicates that an entity originated or started as part of a particular franchise.
- 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_69f349436ee88190b72ee12d0f3f508e |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6f38159d08190980ad639e08f00f4 |
completed | May 3, 2026, 7:04 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d7bee48190b94e0beb48a1d7fa |
completed | May 3, 2026, 5:57 a.m. |
Created at: May 1, 2026, 1:18 a.m.