Triple
T4530
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tymshare |
E87
|
entity |
| Predicate | technologyParadigm |
P480
|
FINISHED |
| Object | time-sharing on large central computers |
—
|
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: time-sharing on large central computers | Statement: [Tymshare, technologyParadigm, time-sharing on large central computers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: technologyParadigm Context triple: [Tymshare, technologyParadigm, time-sharing on large central computers]
-
A.
computes
Indicates that one entity performs a calculation or processing operation to produce a result from given data or inputs.
-
B.
introducedConcept
Indicates that one entity is responsible for presenting, defining, or bringing a new concept into use or awareness for another entity or context.
-
C.
theme
Indicates the entity that is the primary participant or content affected or characterized by an action, event, or state.
-
D.
developedAt
Indicates the place or location where something was created, built, or developed.
-
E.
sector
Indicates that an entity operates in, belongs to, or is associated with a particular economic or industrial sector.
- 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_69a238d6b47881909e68288aed2fd858 |
completed | Feb. 28, 2026, 12:37 a.m. |
| NER | Named-entity recognition | batch_69a23c24b3d08190a714126292fd5479 |
completed | Feb. 28, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69a23998af288190855f0456740cbd51 |
completed | Feb. 28, 2026, 12:40 a.m. |
| PDg | Predicate description generation | batch_69a23c23fef88190ba5d6d86acd4a66f |
completed | Feb. 28, 2026, 12:51 a.m. |
Created at: Feb. 28, 2026, 12:40 a.m.