Triple
T9073268
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mac OS Platinum |
E217419
|
entity |
| Predicate | visualEra |
P86807
|
FINISHED |
| Object | late 1990s Apple software design |
—
|
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 1990s Apple software design | Statement: [Mac OS Platinum, visualEra, late 1990s Apple software design]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: visualEra Context triple: [Mac OS Platinum, visualEra, late 1990s Apple software design]
-
A.
discoveryEra
Indicates the historical period or era during which the entity was discovered or first identified.
-
B.
historical era
Indicates the broad historical period or epoch during which an entity, event, or phenomenon took place or is associated.
-
C.
historicalEraRecreated
Indicates that a past historical era has been reconstructed or simulated, typically for representation, study, or experiential purposes.
-
D.
notableEra
Indicates the historical period or era for which an entity is especially recognized or significant.
-
E.
fictionalEra
Indicates the time period or age within a fictional or imaginary setting in which an entity exists or an event occurs.
- 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_69ca83d6c14c8190bc056d927f00a2a2 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc956111dc8190a25cefe68fd6a949 |
completed | April 1, 2026, 3:47 a.m. |
| PD | Predicate disambiguation | batch_69cc65f881248190bfd220bb28a9fb5f |
completed | April 1, 2026, 12:25 a.m. |
| PDg | Predicate description generation | batch_69cc668ad3d881908a8a93a6a1d553e4 |
completed | April 1, 2026, 12:27 a.m. |
Created at: March 30, 2026, 7:12 p.m.