Triple
T7387493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Intel 4001 |
E170417
|
entity |
| Predicate | programmability |
P76293
|
FINISHED |
| Object | mask-programmable |
—
|
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: mask-programmable | Statement: [Intel 4001, programmability, mask-programmable]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: programmability Context triple: [Intel 4001, programmability, mask-programmable]
-
A.
programmatic
Indicates that one entity is created, controlled, or executed through code or automated software instructions rather than through manual or interactive means.
-
B.
programmedVia
Indicates that one entity is created, configured, or made to operate through the use of another entity as its programming method, tool, or medium.
-
C.
programming
Indicates that an entity writes, develops, or modifies software or code, typically using a programming language to create or control computer programs.
-
D.
program
Indicates that an entity creates, writes, or develops a computer program or software application.
-
E.
programmingLanguage
Indicates that one entity is a programming language used to create, control, or interact with the other 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_69c68a5e2c9081909e713ce866e0060a |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f1f2bac481908ac74069182a4ce4 |
completed | March 27, 2026, 9:09 p.m. |
| PD | Predicate disambiguation | batch_69c6f0309cc88190b55d278969400294 |
completed | March 27, 2026, 9:01 p.m. |
| PDg | Predicate description generation | batch_69c6f0be2b1c8190bea06100a7caef2b |
completed | March 27, 2026, 9:03 p.m. |
Created at: March 27, 2026, 3:08 p.m.