Triple
T29938532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MRG32k3a generator |
E760432
|
entity |
| Predicate | hasYearIntroduced |
P3297
|
FINISHED |
| Object | late 1990s |
—
|
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 | Statement: [MRG32k3a generator, hasYearIntroduced, late 1990s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasYearIntroduced Context triple: [MRG32k3a generator, hasYearIntroduced, late 1990s]
-
A.
introducedInYear
chosen
Indicates the year in which something was first introduced, launched, or made available.
-
B.
reintroducedInYear
Indicates that an entity, previously absent or discontinued, was brought back or reinstated in a specified year.
-
C.
areIntroducedBy
Indicates that one entity becomes known or presented to another entity through the action or mediation of a third party or process.
-
D.
demonstrationYear
Indicates the year in which a demonstration, display, or public showing of something took place.
-
E.
introducedInPublicationYear
Indicates the year in which something (such as a concept, method, or product) was first introduced or presented in a publication.
- 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_69f22463f3648190a603c3ff305c660b |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f677d7ab2c8190a26f161c559ed05b |
completed | May 2, 2026, 10:16 p.m. |
| PD | Predicate disambiguation | batch_69f66ec8298c8190b41fe9d182c05676 |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 6:21 p.m.