Triple
T28582807
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zbt (ternary bit-manipulation) |
E723421
|
entity |
| Predicate | targetSoftwareDomain |
P37802
|
FINISHED |
| Object | systems programming |
—
|
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: systems programming | Statement: [Zbt (ternary bit-manipulation), targetSoftwareDomain, systems programming]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetSoftwareDomain Context triple: [Zbt (ternary bit-manipulation), targetSoftwareDomain, systems programming]
-
A.
targetedSoftware
Indicates that a particular piece of software is the specific focus or target of an action, operation, or effect.
-
B.
softwareDomain
chosen
Indicates that something belongs to, operates within, or is associated with a particular area or field of software.
-
C.
softwareCategoryFocus
Indicates that something is primarily concerned with, or directed toward, a particular category or type of software.
-
D.
developedForDomain
Indicates that something was created, designed, or tailored specifically to be used within or to address the needs of a particular domain or field.
-
E.
targetsEcosystem
Indicates that an action, product, or policy is directed toward, affects, or is specifically intended for a particular ecosystem.
- 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_69f01d7f92e481909847f5f3f3174a89 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f7979a073881909a4fde2558e6b6f3 |
completed | May 3, 2026, 6:44 p.m. |
| PD | Predicate disambiguation | batch_69f7961550f88190b7bb8a9155458b54 |
completed | May 3, 2026, 6:38 p.m. |
Created at: April 28, 2026, 4:16 a.m.