Triple
T29343368
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SuperCalc |
E744095
|
entity |
| Predicate | genrePioneer |
P172151
|
FINISHED |
| Object | microcomputer spreadsheet software |
—
|
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: microcomputer spreadsheet software | Statement: [SuperCalc, genrePioneer, microcomputer spreadsheet software]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: genrePioneer Context triple: [SuperCalc, genrePioneer, microcomputer spreadsheet software]
-
A.
genreIncludes
Indicates that a broader genre category encompasses or contains a specified subgenre or work as part of its classification.
-
B.
genreSpecialty
Indicates that an entity specializes in or is particularly associated with a specific genre.
-
C.
genreAsModel
Indicates that one entity serves as a genre-based template or stylistic model for another entity.
-
D.
musicGenreCategory
Indicates that one entity is a broader music genre category under which the other music genre is classified.
-
E.
genreDiversity
Indicates the extent to which an entity involves, includes, or spans multiple distinct genres rather than being confined to a single genre.
- 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_69f09126cfcc8190899b16fbf3c2bf7b |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f6a9603b208190b3533ea2b441514c |
completed | May 3, 2026, 1:48 a.m. |
| PD | Predicate disambiguation | batch_69f6a751d5e48190a77dcecbe7ef9f0b |
completed | May 3, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f6a8de0b948190ae333e9cd99cbf6c |
completed | May 3, 2026, 1:46 a.m. |
Created at: April 28, 2026, 1:35 p.m.