Triple
T35647732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earth–Romulan War |
E1030054
|
entity |
| Predicate | technologyInvolved |
P41521
|
FINISHED |
| Object | warp drive |
—
|
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: warp drive | Statement: [Earth–Romulan War, technologyInvolved, warp drive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: technologyInvolved Context triple: [Earth–Romulan War, technologyInvolved, warp drive]
-
A.
technologyIncludes
Indicates that one technology encompasses, contains, or incorporates another technology as part of its components, features, or implementation.
-
B.
technologyDiscussed
Indicates that a conversation, text, or interaction includes discussion or mention of a particular technology.
-
C.
technologyUsedIn
chosen
Indicates that a particular technology is employed or applied within a specific process, product, context, or domain.
-
D.
technologyPresent
Indicates that a particular technology exists, is available, or is currently in use in the given context or situation.
-
E.
technologyType
Indicates the specific kind or category of technology associated with an entity or relationship.
- 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_69f76e0938088190a8f199631e97dec3 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79f52590c8190bb87a89ccbff1a87 |
completed | May 3, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f79e4d885881908a3612e2e75cf84f |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:05 p.m.