Triple
T38221685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Borg transwarp conduit |
E1012025
|
entity |
| Predicate | energySignature |
P190309
|
FINISHED |
| Object | distinct Borg transwarp signature |
—
|
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: distinct Borg transwarp signature | Statement: [Borg transwarp conduit, energySignature, distinct Borg transwarp signature]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: energySignature Context triple: [Borg transwarp conduit, energySignature, distinct Borg transwarp signature]
-
A.
energyStandard
Indicates that an entity complies with, is classified by, or is governed according to a specified energy-related standard or efficiency criterion.
-
B.
energyUtilization
Indicates how effectively an entity uses available energy to perform work or sustain its functions.
-
C.
energyUse
Indicates the amount or rate at which an entity consumes energy to perform its functions or activities.
-
D.
energyEfficiencyList
Indicates that an entity is included in a list or classification based on its level of energy efficiency.
-
E.
energyImplication
Indicates that one state, action, or condition entails or leads to a particular outcome in terms of energy use, transfer, or impact.
- F. None of above. chosen
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_69f76dd25e0c81909f2abd0803e5e3ee |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcc42cbac48190b8d3e4c9ce140838 |
completed | May 7, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69fcb0fc69c88190800453eb57a7e62c |
completed | May 7, 2026, 3:34 p.m. |
| PDg | Predicate description generation | batch_69fcc42b9334819099929649b7ef68ea |
completed | May 7, 2026, 4:56 p.m. |
Created at: May 3, 2026, 4:30 p.m.