Triple
T34957933
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EMH |
E1008168
|
entity |
| Predicate | mobileEmitterOrigin |
P40631
|
FINISHED |
| Object | 29th-century 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: 29th-century technology | Statement: [EMH, mobileEmitterOrigin, 29th-century technology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mobileEmitterOrigin Context triple: [EMH, mobileEmitterOrigin, 29th-century technology]
-
A.
electronSource
Indicates a relationship where one entity serves as the origin or provider of electrons for another entity or process.
-
B.
signalOrigin
chosen
Indicates that one entity is the source or starting point from which a signal is generated or transmitted to others.
-
C.
transmittedFrom
Indicates that something (such as information, a signal, or a disease) has been passed or conveyed from one source entity to another.
-
D.
originPlatform
Indicates the platform, system, or environment from which an entity, event, or piece of data originally comes.
-
E.
missionOrigin
Indicates the place, organization, or context from which a mission is initiated or originates.
- 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_69f76dc69564819099e9e78aed6ff0a6 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78fd5a6388190bfda4bbb2e222e5b |
completed | May 3, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_69f78e2ac3fc819081a45c6841375c8d |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4 p.m.