Triple
T38344145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LCARS |
E1041491
|
entity |
| Predicate | notableVesselUsage |
P3345
|
FINISHED |
| Object | USS Enterprise-D |
E302632
|
NE 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: USS Enterprise-D | Statement: [LCARS, notableVesselUsage, USS Enterprise-D]
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 (4 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_69f76e2ad95481908c920c0e5c1c3e26 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a41a7f5331c8190ace7af7eea0e52d4 |
completed | June 28, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_6a037a1c850c819088795a7ae59bdeb8 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:30 p.m.