Triple
T28582795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zbt (ternary bit-manipulation) |
E723421
|
entity |
| Predicate | architectureDomain |
P178294
|
FINISHED |
| Object | RISC-V |
—
|
NE NERFINISHED |
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: RISC-V | Statement: [Zbt (ternary bit-manipulation), architectureDomain, RISC-V]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: architectureDomain Context triple: [Zbt (ternary bit-manipulation), architectureDomain, RISC-V]
-
A.
architecture
Indicates the structural design or organizational framework that defines how components of a system or entity are arranged and interact.
-
B.
architectureType
Indicates the specific style or category of architecture that characterizes or defines an entity.
-
C.
architectureName
Indicates the specific name or title assigned to an architecture.
-
D.
toArchitecture
Indicates a relationship in which something is designed, structured, or organized according to a particular architectural style, plan, or system.
-
E.
architecturalPlanner
Indicates a relationship where an entity is responsible for designing, organizing, or planning the architectural structure or layout of 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_69f01d7f92e481909847f5f3f3174a89 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f70e8755a48190931eaa77946f9460 |
completed | May 3, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f70abc00848190a1c3f495ef6c8dc6 |
completed | May 3, 2026, 8:43 a.m. |
| PDg | Predicate description generation | batch_69f70e854b9c8190a3416e2189e17742 |
completed | May 3, 2026, 8:59 a.m. |
Created at: April 28, 2026, 4:16 a.m.