Triple
T14645693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UltraSPARC II |
E343842
|
entity |
| Predicate | typicalApplicationDomain |
P24492
|
FINISHED |
| Object | enterprise computing |
—
|
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: enterprise computing | Statement: [UltraSPARC II, typicalApplicationDomain, enterprise computing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalApplicationDomain Context triple: [UltraSPARC II, typicalApplicationDomain, enterprise computing]
-
A.
typicalDomain
chosen
Indicates that one entity is the characteristic or most common domain, context, or area of application in which another entity typically occurs or is used.
-
B.
standardDomain
Indicates that something belongs to, or is defined within, the usual or default domain of discourse or applicability for a given context.
-
C.
typicalApplicationWindow
Indicates that something is a standard or commonly used application window in a software environment.
-
D.
defaultDomain
Indicates that one entity serves as the standard or primary domain associated with another entity, used when no more specific domain is specified.
-
E.
commonApplication
Indicates that multiple entities share or participate in the same application, process, or usage context.
- 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_69d822e1a2cc81908e5bb93cf61ce3cc |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb4ea6d8481908e6331ca173c646b |
completed | April 14, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69de657359c88190b082e3e9f86fc1d7 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:26 a.m.