Triple
T20790678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Enterprise (NCC-1701-D) |
E511764
|
entity |
| Predicate | computerSystem |
P52453
|
FINISHED |
| Object | LCARS |
—
|
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: LCARS | Statement: [USS Enterprise (NCC-1701-D), computerSystem, LCARS]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: LCARS Context triple: [USS Enterprise (NCC-1701-D), computerSystem, LCARS]
-
A.
LCARS
chosen
LCARS is the iconic, touch-based computer operating system and user interface used throughout Starfleet vessels in the Star Trek universe.
-
B.
NCC-1031
NCC-1031 is the registry number of the Crossfield-class starship USS Discovery featured in the television series Star Trek: Discovery.
-
C.
Enterprise NX-01
Enterprise NX-01 is the first Warp 5-capable starship of the United Earth Starfleet, featured in Star Trek: Enterprise as humanity’s pioneering deep-space exploration vessel.
-
D.
AT-X
AT-X is a Japanese premium television network specializing in broadcasting anime and related programming.
-
E.
NCC-1227
NCC-1227 is the registry designation of the USS Shenzhou, a Walker-class Federation starship commanded by Captain Philippa Georgiou in Star Trek: Discovery.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b4cb83948190bd57bec21d78ed53 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c29010508190bf2cf577d7f64754 |
completed | April 21, 2026, 12:19 a.m. |
Created at: April 16, 2026, 12:38 p.m.