Triple
T35103330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USS Excelsior |
E1013079
|
entity |
| Predicate | experimentalTechnology |
P14232
|
FINISHED |
| Object | transwarp drive |
—
|
NE NERFINISHED |
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: transwarp drive | Statement: [USS Excelsior, experimentalTechnology, transwarp drive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: experimentalTechnology Context triple: [USS Excelsior, experimentalTechnology, transwarp drive]
-
A.
envisionedTechnology
Indicates that an entity has imagined, conceptualized, or planned a particular technology, typically before it exists or is realized.
-
B.
technologyPresent
Indicates that a particular technology exists, is available, or is currently in use in the given context or situation.
-
C.
technologyPioneered
chosen
Indicates that an entity was the first or among the first to develop, introduce, or significantly advance a particular technology.
-
D.
laterUsedTechnology
Indicates that one entity adopted or employed a technology after another entity had already used it.
-
E.
technologyDiscussed
Indicates that a conversation, text, or interaction includes discussion or mention of a particular technology.
- 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_69f76dd556248190808b4c4f43debebb |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78ce78b508190955848e133398dc8 |
completed | May 3, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69f78b8f4cc08190b49fccd798cb25d7 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4:01 p.m.