Triple
T8690944
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sun-4 workstation |
E206285
|
entity |
| Predicate | widelyUsedInPeriod |
P3656
|
FINISHED |
| Object | late 1980s |
—
|
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: late 1980s | Statement: [Sun-4 workstation, widelyUsedInPeriod, late 1980s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: widelyUsedInPeriod Context triple: [Sun-4 workstation, widelyUsedInPeriod, late 1980s]
-
A.
widelyUsedIn
Indicates that something is commonly or extensively utilized within a particular context, domain, or group.
-
B.
historicalPeriodOfUse
chosen
Indicates the time period during which something was in active use or commonly utilized.
-
C.
firstWidelyUsedDuring
Indicates that something (such as a concept, technology, or practice) came into its first period of broad or widespread use during a specified time or era.
-
D.
periodOfMajorUse
Indicates the time span during which something was primarily or most intensively used.
-
E.
wasDevelopedInPeriod
Indicates that something was created, produced, or brought into existence during a specified time period.
- 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_69ca835481fc819084e33d3bc883bfa6 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5735ffdc819094126e2698f98511 |
completed | March 31, 2026, 11:22 p.m. |
| PD | Predicate disambiguation | batch_69cc4569f9048190b9c86b4c81103d35 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:33 p.m.