Triple
T17863358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anthony Rapp as Paul Stamets |
E446127
|
entity |
| Predicate | technologyAssociatedWith |
P1485
|
FINISHED |
| Object | spore 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: spore drive | Statement: [Anthony Rapp as Paul Stamets, technologyAssociatedWith, spore drive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: technologyAssociatedWith Context triple: [Anthony Rapp as Paul Stamets, technologyAssociatedWith, spore drive]
-
A.
technologyUsedBy
Indicates that a particular technology is employed or utilized by a specified entity.
-
B.
technologyUsedIn
Indicates that a particular technology is employed or applied within a specific process, product, context, or domain.
-
C.
technologyUsedFor
Indicates that a particular technology is employed or applied to accomplish, support, or enable a specific purpose, task, or function.
-
D.
associatedWithTechnology
chosen
Indicates a relationship where an entity is connected to, involved with, or utilizes a particular technology.
-
E.
technologyInteractedWith
Indicates that an entity has used, engaged with, or otherwise interacted with 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_69d8b9f26f18819089c9e43250bee6ae |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e49791b0c08190b04a426bd274065d |
completed | April 19, 2026, 8:51 a.m. |
| PD | Predicate disambiguation | batch_69e3d8e6d2e88190ad9ef9f8a99f13e6 |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:17 a.m.