Triple
T25240328
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | T’Pol |
E632445
|
entity |
| Predicate | seriesFirstAppearance |
P160958
|
FINISHED |
| Object | Star Trek: Enterprise 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: Star Trek: Enterprise season 1 | Statement: [T’Pol, seriesFirstAppearance, Star Trek: Enterprise season 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seriesFirstAppearance Context triple: [T’Pol, seriesFirstAppearance, Star Trek: Enterprise season 1]
-
A.
mainSeriesFirstAppearance
chosen
Indicates the work or installment in which an entity first appears within the primary or main series continuity.
-
B.
seriesOrderOfFirstAppearance
Indicates the position in which an entity first appears within a series, relative to other entities in that same series.
-
C.
yearOfFirstApparition
Indicates the calendar year in which the entity first appeared or was introduced.
-
D.
airDateOfFirstAppearance
Indicates the calendar date on which an entity (such as a character, show, or episode) was first broadcast or made publicly available.
-
E.
seriesDebut
Indicates the first appearance or initial release of a series in which the subject entity is introduced.
- 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_69e75a8ec5f88190b9eba06ae42b413a |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f627aedf548190bc9f53c8a2d67b50 |
completed | May 2, 2026, 4:34 p.m. |
| PD | Predicate disambiguation | batch_69f623a4e1048190bbb8dd1253fdcee9 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 21, 2026, 1:07 p.m.