Triple
T29589767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MF 19 |
E754118
|
entity |
| Predicate | replacesSeries |
P184857
|
FINISHED |
| Object | previous-generation MF-series stock |
—
|
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: previous-generation MF-series stock | Statement: [MF 19, replacesSeries, previous-generation MF-series stock]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacesSeries Context triple: [MF 19, replacesSeries, previous-generation MF-series stock]
-
A.
usesSeriesName
Indicates that one entity employs or refers to the series name associated with another entity.
-
B.
seriesMove
Indicates a relationship where one entity is moved, transferred, or progresses as part of a sequence or series of related steps or positions.
-
C.
leavesSeriesWith
Indicates that an entity departs from or exits a series, sequence, or collection, ending its participation in that series.
-
D.
givesSeriesFor
Indicates that one entity provides or assigns a series (such as a sequence, set, or collection) to another entity.
-
E.
seriesWith
Indicates that one entity is part of, or grouped together in, the same series or sequence as another entity.
- 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_69f0ef836ac88190bd809dc58b5ec907 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f7b628b17c8190aa058c1a51852a27 |
completed | May 3, 2026, 8:55 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c06f5881908f0b98cad6796478 |
completed | May 3, 2026, 8:49 p.m. |
| PDg | Predicate description generation | batch_69f7b5cadd308190a864245a21b08f9a |
completed | May 3, 2026, 8:53 p.m. |
Created at: April 28, 2026, 6:13 p.m.