Triple
T28609444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NetWare |
E724135
|
entity |
| Predicate | originalArchitecture |
P198648
|
FINISHED |
| Object | 16-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: 16-bit | Statement: [NetWare, originalArchitecture, 16-bit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalArchitecture Context triple: [NetWare, originalArchitecture, 16-bit]
-
A.
previousArchitecture
Indicates that one architecture served as the predecessor or earlier version of another architecture in a sequence or evolution.
-
B.
architecturalOrigin
Indicates the place, style, or tradition from which an architectural work or design originates.
-
C.
buildingArchitectOfOriginal
Indicates that an entity is the architect responsible for the original design of a particular building.
-
D.
laterArchitecture
Indicates that one architectural style, structure, or design chronologically follows and is influenced by another.
-
E.
originalBuilding
Indicates that a building is the initial or first version from which later buildings, modifications, or replacements are derived.
- 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_69fefa064ab48190925759950d0d94d9 |
completed | May 9, 2026, 9:10 a.m. |
| PD | Predicate disambiguation | batch_69fef96ae5d08190b027435753c44821 |
completed | May 9, 2026, 9:07 a.m. |
| PDg | Predicate description generation | batch_69fefa05757481908fa38f5c604afbbe |
completed | May 9, 2026, 9:10 a.m. |
Created at: April 28, 2026, 4:29 a.m.