Triple
T37769227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Erista |
E941494
|
entity |
| Predicate | successorSoC |
P202766
|
FINISHED |
| Object | Tegra X1+ (Mariko) |
—
|
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: Tegra X1+ (Mariko) | Statement: [Erista, successorSoC, Tegra X1+ (Mariko)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: successorSoC Context triple: [Erista, successorSoC, Tegra X1+ (Mariko)]
-
A.
successorSystem
Indicates that one system directly follows and replaces another in function, role, or version.
-
B.
successorSoftware
Indicates that one software product directly follows and replaces another as its newer version or update.
-
C.
successor
Indicates that one entity directly follows another in an ordered sequence or position.
-
D.
successorCore
Indicates that one entity directly follows another in a defined sequence or ordered progression.
-
E.
successorEngine
Indicates that one engine directly follows and replaces another in a sequence or version lineage.
- 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_69f76ee3251881909bb4451aad50752b |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a00b6199c348190b1e90375f737d026 |
completed | May 10, 2026, 4:45 p.m. |
| PD | Predicate disambiguation | batch_6a00b5169a7881909a07167c4188731f |
completed | May 10, 2026, 4:40 p.m. |
| PDg | Predicate description generation | batch_6a00b618cb10819095ccef12d8e303c5 |
completed | May 10, 2026, 4:45 p.m. |
Created at: May 3, 2026, 4:19 p.m.