Triple
T35959579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tofu Interconnect D |
E1039958
|
entity |
| Predicate | subsequentVersionOf |
P47516
|
FINISHED |
| Object | Tofu Interconnect 2 |
—
|
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: Tofu Interconnect 2 | Statement: [Tofu Interconnect D, subsequentVersionOf, Tofu Interconnect 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subsequentVersionOf Context triple: [Tofu Interconnect D, subsequentVersionOf, Tofu Interconnect 2]
-
A.
hasSubsequentVersion
Indicates that one entity is a later or updated version that follows another entity in a version sequence.
-
B.
isVersionOf
Indicates that one entity is a particular version, edition, or variant derived from another entity.
-
C.
laterVersion
chosen
Indicates that one entity is a subsequent or more recent version of another entity in a version sequence.
-
D.
isAbstractVersionOf
Indicates that one entity represents a conceptual, generalized, or non-concrete version of another, more specific or concrete entity.
-
E.
isTemporaryVersionOf
Indicates that one entity is a non-final, short-lived or provisional form of another, more permanent entity.
- 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_69f76e26b21081909fd9ffb3aff6c77a |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7b2c771108190adeec151daad5dab |
completed | May 3, 2026, 8:40 p.m. |
| PD | Predicate disambiguation | batch_69f7b1bad2e88190963ab4ee5d4f2038 |
completed | May 3, 2026, 8:36 p.m. |
Created at: May 3, 2026, 4:07 p.m.