Triple
T35183956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quickoffice |
E1015931
|
entity |
| Predicate | originalReleaseApproximateYear |
P49730
|
FINISHED |
| Object | 2000s |
—
|
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: 2000s | Statement: [Quickoffice, originalReleaseApproximateYear, 2000s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalReleaseApproximateYear Context triple: [Quickoffice, originalReleaseApproximateYear, 2000s]
-
A.
releaseApproximateYear
chosen
Indicates that an entity was released or made available around a specified year, where the year is approximate rather than exact.
-
B.
fullReleaseYear
Indicates the calendar year in which something is fully released or made publicly available in its complete form.
-
C.
approximatePremiereYear
Indicates the estimated calendar year in which something, typically a work or event, first premiered.
-
D.
originYear
Indicates the year in which something first originated, was created, or began.
-
E.
singleReleaseYear
Indicates the year in which a particular single (song) was officially released.
- 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_69f76ddd815c8190b822eea06630f9fb |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a016960819093ed4990fb4d9d36 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:02 p.m.