Triple
T25186669
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enterprise NX-01 |
E630735
|
entity |
| Predicate | designInfluenceFor |
P44042
|
FINISHED |
| Object | later Federation starship designs |
—
|
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: later Federation starship designs | Statement: [Enterprise NX-01, designInfluenceFor, later Federation starship designs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designInfluenceFor Context triple: [Enterprise NX-01, designInfluenceFor, later Federation starship designs]
-
A.
designInfluenceOn
chosen
Indicates that one design, designer, or design-related factor has an effect on shaping, guiding, or altering another design or design outcome.
-
B.
designUse
Indicates that one entity is used as a design basis, purpose, or intended functional use for another entity.
-
C.
helpsDesign
Indicates that one entity assists or contributes to another entity’s design or design process.
-
D.
creativeInfluence
Indicates that one entity has shaped, inspired, or informed the creative work, style, or ideas of another entity.
-
E.
designTrend
Indicates a prevailing or emerging stylistic direction or pattern that influences how something is designed over a period of time.
- 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_69e75a8a6d088190ba1e82a4345225e7 |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f638d11c988190af7fd4572b08e038 |
completed | May 2, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69f63706b6008190993577193c85ff50 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 21, 2026, 12:44 p.m.