Triple
T10372221
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NORD-500 |
E244410
|
entity |
| Predicate | computingRole |
P24646
|
FINISHED |
| Object | multi-user system |
—
|
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: multi-user system | Statement: [NORD-500, computingRole, multi-user system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: computingRole Context triple: [NORD-500, computingRole, multi-user system]
-
A.
computingModel
Indicates the computational framework, paradigm, or formal system used to perform or describe a computation.
-
B.
technologyRole
chosen
Indicates the functional role or purpose that a technology plays within a system, process, or context.
-
C.
computes
Indicates that one entity performs a calculation or processing operation to produce a result from given data or inputs.
-
D.
complexityRole
Indicates a relationship where an entity’s role or function is characterized or classified in terms of its complexity level.
-
E.
hardwareRole
Indicates the functional role or purpose that a piece of hardware serves within a system or configuration.
- 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_69d381b3e328819094b23b8edcd29b5a |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e97ed09c8190a3627aa7b5eea62f |
completed | April 7, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69d4dface5508190a7b42f01ad0a19a2 |
completed | April 7, 2026, 10:42 a.m. |
Created at: April 6, 2026, 12:01 p.m.