Triple
T29812302
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Transistor |
E756998
|
entity |
| Predicate | predecessorByDeveloper |
P85947
|
FINISHED |
| Object | Bastion |
—
|
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: Bastion | Statement: [Transistor, predecessorByDeveloper, Bastion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: predecessorByDeveloper Context triple: [Transistor, predecessorByDeveloper, Bastion]
-
A.
predecessorCompiledBy
Indicates that one entity was compiled by the same agent or process before another entity was compiled.
-
B.
predecessorName
Indicates that the value is the name of an entity that directly precedes another in an ordered sequence or lineage.
-
C.
formerlyDevelopedBy
chosen
Indicates that an entity was developed in the past by another entity, but is no longer developed by that same party.
-
D.
predecessorDesign
Indicates that one design serves as the predecessor or earlier version in relation to another design.
-
E.
predecessorRealName
Indicates that one entity is the real (actual) name of the predecessor of another 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_69f2245584848190ad4cab1f07752ccb |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f7b2f3a104819098ddd8909eaf596c |
completed | May 3, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f7b1b8a9fc8190a1279e67a2d12707 |
completed | May 3, 2026, 8:36 p.m. |
Created at: April 29, 2026, 5:24 p.m.