Triple
T31583814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eclipse MV/8000 |
E805894
|
entity |
| Predicate | commercialAvailabilityPeriod |
P97306
|
FINISHED |
| Object | early 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: early 1980s | Statement: [Eclipse MV/8000, commercialAvailabilityPeriod, early 1980s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commercialAvailabilityPeriod Context triple: [Eclipse MV/8000, commercialAvailabilityPeriod, early 1980s]
-
A.
commercialAvailability
Indicates that an entity is offered for sale or otherwise obtainable through commercial channels.
-
B.
announcedAvailability
Indicates that an entity has publicly communicated that something will be obtainable or accessible, typically starting at a specified time or under certain conditions.
-
C.
availabilityEnd
Indicates the point in time or condition after which something is no longer available or offered.
-
D.
availabilityStart
Indicates the date and time from which something becomes available or active.
-
E.
availabilityPeriod
chosen
Indicates the time span during which something is available or valid for use.
- 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_69f348d3a86c8190a3e5e539a4dd125f |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f73223675481908c1bc3208c0f5284 |
completed | May 3, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69f7317690108190b3aae2cd2e1d069e |
completed | May 3, 2026, 11:28 a.m. |
Created at: April 30, 2026, 10:24 p.m.