Triple
T7304497
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zilog Z80 |
E167939
|
entity |
| Predicate | fabricationTechnology |
P76106
|
FINISHED |
| Object | NMOS |
—
|
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: NMOS | Statement: [Zilog Z80, fabricationTechnology, NMOS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fabricationTechnology Context triple: [Zilog Z80, fabricationTechnology, NMOS]
-
A.
fabricationPartner
Indicates a relationship where one entity serves as a manufacturing or production collaborator responsible for fabricating another entity’s designs, components, or products.
-
B.
mainGenerationTechnology
Indicates the primary technology or method used to generate something, typically identifying the dominant production or generation approach among possible alternatives.
-
C.
coFabricator
Indicates that two or more entities jointly fabricate, construct, or produce something together.
-
D.
fabricatedOn
Indicates that something was manufactured, constructed, or produced at a specific time or date.
-
E.
technologicalFeature
Indicates that one entity possesses, exhibits, or is characterized by a specific technological capability, component, or functionality in relation to another entity.
- F. None of above. chosen
Provenance (4 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_69c6888c820881909fc68f689fe1c251 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6ebb352ec8190846eff044e08805e |
completed | March 27, 2026, 8:42 p.m. |
| PD | Predicate disambiguation | batch_69c6e76e67d88190bd3ca6864f45845a |
completed | March 27, 2026, 8:24 p.m. |
| PDg | Predicate description generation | batch_69c6eb2d4c0c8190b4cc6fdfdb7f4827 |
completed | March 27, 2026, 8:40 p.m. |
Created at: March 27, 2026, 3:01 p.m.