Triple
T4176703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Ship |
E86493
|
entity |
| Predicate | technologyOfOrigin |
P50245
|
FINISHED |
| Object | Time Lord technology |
—
|
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: Time Lord technology | Statement: [The Ship, technologyOfOrigin, Time Lord technology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: technologyOfOrigin Context triple: [The Ship, technologyOfOrigin, Time Lord technology]
-
A.
technologyOrigin
chosen
Indicates that one entity is the source, creator, or originating context of a particular technology associated with another entity.
-
B.
technologyType
Indicates the specific kind or category of technology associated with an entity or relationship.
-
C.
originallyDevelopedFor
Indicates that something was first created, designed, or produced with the primary purpose of serving a particular use, user group, context, or application.
-
D.
technologyPioneered
Indicates that an entity was the first or among the first to develop, introduce, or significantly advance a particular technology.
-
E.
technologyBasis
Indicates that one entity is founded on, enabled by, or fundamentally relies upon the technology provided or represented by another entity.
- 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_69aed93de98c8190ad838ce507b77c8a |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af07078cb081909f64326b12522410 |
completed | March 9, 2026, 5:44 p.m. |
| PD | Predicate disambiguation | batch_69af019155448190b19868583272513f |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:45 p.m.