Triple
T38344145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LCARS |
E1041491
|
entity |
| Predicate | notableVesselUsage |
—
|
GENERATED |
| Object | USS Enterprise-D |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableVesselUsage Context triple: [LCARS, notableVesselUsage, USS Enterprise-D]
-
A.
notableVesselBuilt
Indicates that a particular vessel was constructed by or for the subject and is notable or significant in that context.
-
B.
shipsUsedAs
Indicates that certain ships are employed or repurposed to serve in a specified role, function, or capacity.
-
C.
namedVesselOf
Indicates that one entity is the specific named vessel (e.g., ship, boat, or craft) associated with or belonging to another entity.
-
D.
notableShip
chosen
Indicates that there is a notable or significant ship associated with the subject entity.
-
E.
vesselTypeServedOn
Indicates the type of vessel on which an entity has served or performed duty.
- F. None of above.
Provenance (1 batch)
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_69f76e2ad95481908c920c0e5c1c3e26 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:30 p.m.