Triple
T28609445
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NetWare |
E724135
|
entity |
| Predicate | laterArchitecture |
P194983
|
FINISHED |
| Object | 32-bit |
—
|
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: 32-bit | Statement: [NetWare, laterArchitecture, 32-bit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterArchitecture Context triple: [NetWare, laterArchitecture, 32-bit]
-
A.
previousArchitecture
Indicates that one architecture served as the predecessor or earlier version of another architecture in a sequence or evolution.
-
B.
subsequentArchitect
Indicates that one architect comes after another in a temporal or sequential order, such as in a series of design or construction roles.
-
C.
architecturalLegacyIn
Indicates that an entity has left a lasting architectural influence, style, or heritage within a specified place or region.
-
D.
previousArchitecturalStyle
Indicates that one architectural style directly preceded another in the historical or developmental sequence of a building or design.
-
E.
toArchitecture
Indicates a relationship in which something is designed, structured, or organized according to a particular architectural style, plan, or system.
- 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_69f01d816d7c8190a1fe27e3434041dc |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69fd974d75e08190af46b1d608769f3b |
completed | May 8, 2026, 7:57 a.m. |
| PD | Predicate disambiguation | batch_69fd94ff792c8190bedf4a639d3da809 |
completed | May 8, 2026, 7:47 a.m. |
| PDg | Predicate description generation | batch_69fd974c0e8481909fdd312897c647b3 |
completed | May 8, 2026, 7:57 a.m. |
Created at: April 28, 2026, 4:29 a.m.