Triple
T37493578
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Performa 5260CD |
E931763
|
entity |
| Predicate | predecessorModelFamily |
P44839
|
FINISHED |
| Object | Performa 52xx series |
—
|
NE NERFINISHED |
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: Performa 52xx series | Statement: [Performa 5260CD, predecessorModelFamily, Performa 52xx series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: predecessorModelFamily Context triple: [Performa 5260CD, predecessorModelFamily, Performa 52xx series]
-
A.
predecessorModel
Indicates that one model directly precedes another in a sequence, version history, or developmental lineage.
-
B.
predecessorFamily
chosen
Indicates that one family is the earlier or ancestral family from which another family descends or follows.
-
C.
predecessorSystem
Indicates that one system existed or was in use before and was replaced or superseded by another system.
-
D.
predecessorPowerUnitSupplier
Indicates that one power unit supplier previously supplied or held the role before another in a temporal or sequential relationship.
-
E.
predecessorSystemType
Indicates that one system type functioned as the predecessor or earlier version to another system type.
- 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_69f76ec457a4819094eeb3aed9baac11 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fe610e1f6881908f10070ba64643cf |
completed | May 8, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69fe604c6c008190ad659e9b9fa82f7b |
completed | May 8, 2026, 10:14 p.m. |
Created at: May 3, 2026, 4:17 p.m.