Triple
T29046322
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | technetronic society |
E735144
|
entity |
| Predicate | emphasizesTechnologyType |
P88055
|
FINISHED |
| Object | electronics |
—
|
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: electronics | Statement: [technetronic society, emphasizesTechnologyType, electronics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emphasizesTechnologyType Context triple: [technetronic society, emphasizesTechnologyType, electronics]
-
A.
technologyType
Indicates the specific kind or category of technology associated with an entity or relationship.
-
B.
focusTechnology
chosen
Indicates that an entity is centered on, specializes in, or primarily deals with a particular technology.
-
C.
technologicalFeature
Indicates that one entity possesses, exhibits, or is characterized by a specific technological capability, component, or functionality in relation to another entity.
-
D.
technologyClass
Indicates the classification or category of technology to which an entity belongs.
-
E.
equipmentEmphasis
Indicates that particular importance or focus is placed on certain equipment within a given context or activity.
- 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_69f077e64b88819094d37bdbca8191b3 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6606204508190afe4f34752bb682a |
completed | May 2, 2026, 8:36 p.m. |
| PD | Predicate disambiguation | batch_69f659d297cc8190b2b962ba30a1edb3 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 10:05 a.m.