Triple
T25240184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Star Trek: Titan |
E632442
|
entity |
| Predicate | mainStarship |
P108461
|
FINISHED |
| Object | USS Titan |
—
|
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: USS Titan | Statement: [Star Trek: Titan, mainStarship, USS Titan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainStarship Context triple: [Star Trek: Titan, mainStarship, USS Titan]
-
A.
hasStarship
chosen
Indicates that one entity possesses, controls, or is associated with a particular starship.
-
B.
usesStarshipClass
Indicates that an entity operates, employs, or is associated with a particular class or type of starship.
-
C.
hasStarshipClassDepicted
Indicates that an entity includes or shows a depiction of a particular starship class.
-
D.
starshipCommanded
Indicates that one entity serves as the commanding officer or authority in charge of operating and directing the other entity, which is a starship.
-
E.
notableStarfighter
Indicates that an entity is a starfighter recognized for particular significance, prominence, or distinction (e.g., historically, tactically, or culturally).
- 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_69f47dfe32488190b3d19a3196b51c68 |
completed | May 1, 2026, 10:18 a.m. |
| PD | Predicate disambiguation | batch_69f44d849e7c81909945438f40e35362 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 21, 2026, 1:07 p.m.