Triple
T12035390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IBM 604 |
E286523
|
entity |
| Predicate | logicImplementation |
P17357
|
FINISHED |
| Object | vacuum tube |
—
|
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: vacuum tube | Statement: [IBM 604, logicImplementation, vacuum tube]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: logicImplementation Context triple: [IBM 604, logicImplementation, vacuum tube]
-
A.
logicFunction
Indicates a relationship where one entity serves as a logical function or operator that determines the truth value or output based on given inputs or conditions involving another entity.
-
B.
logicType
Indicates the specific kind or category of logical system, rule, or reasoning framework that an entity or statement belongs to.
-
C.
logicSystem
Indicates a relationship where an entity is associated with, defined within, or governed by a particular logical framework or system of formal reasoning.
-
D.
logicFamily
chosen
Indicates the logical circuit family or technology type to which a digital component or device belongs.
-
E.
logicLevelDetermines
Indicates that the specific logic level of one entity determines or dictates the resulting state, behavior, or outcome 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_69d6ab4669e48190b59246358b0383ab |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9100b4ca8819084845ca4c13e34ce |
completed | April 10, 2026, 2:58 p.m. |
| PD | Predicate disambiguation | batch_69d902b6ebbc8190b13c44a61c6f81b9 |
completed | April 10, 2026, 2:01 p.m. |
Created at: April 8, 2026, 9:47 p.m.