Triple
T7163802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Star Trek: Enterprise |
E167013
|
entity |
| Predicate | titleChangeDetail |
P12696
|
FINISHED |
| Object | Renamed from Enterprise to Star Trek: Enterprise |
—
|
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: Renamed from Enterprise to Star Trek: Enterprise | Statement: [Star Trek: Enterprise, titleChangeDetail, Renamed from Enterprise to Star Trek: Enterprise]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: titleChangeDetail Context triple: [Star Trek: Enterprise, titleChangeDetail, Renamed from Enterprise to Star Trek: Enterprise]
-
A.
titleBecomes
Indicates that one title changes into or is replaced by another title over time.
-
B.
retitledAs
chosen
Indicates that an entity has been given a new title or name, replacing or supplementing its original one.
-
C.
titleVariant
Indicates that one title is an alternative or variant form of another title referring to the same work or entity.
-
D.
titleRepresents
Indicates that a given title stands for, denotes, or symbolizes a particular concept, role, work, or entity.
-
E.
title
Indicates that one entity serves as the formal name or designation 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_69c68888c10c819095e0383020225758 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e83168a08190937ff46797d94f3e |
completed | March 27, 2026, 8:27 p.m. |
| PD | Predicate disambiguation | batch_69c6e1cd5c948190a9113b23f7308c21 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:47 p.m.