Triple
T35662563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LM101 operational amplifier |
E1030475
|
entity |
| Predicate | hasOffsetNullCapability |
P44399
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [LM101 operational amplifier, hasOffsetNullCapability, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOffsetNullCapability Context triple: [LM101 operational amplifier, hasOffsetNullCapability, true]
-
A.
hasInputOffsetNullCapability
chosen
Indicates that an entity supports or is capable of handling input values that are null or have no offset.
-
B.
hasOffsetNullPins
Indicates that one entity has pins that are offset from a reference position and intentionally left unconnected or null.
-
C.
hasOffset
Indicates that one entity is displaced or shifted from another by a specified amount, distance, or position.
-
D.
hasNullSet
Indicates that an entity is associated with, contains, or is characterized by an empty or null set of elements.
-
E.
nullValueSupport
Indicates that the relationship or operation explicitly allows, handles, or preserves null (missing) values for the involved entities or attributes.
- 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_69f76e09f87881909c954aaac176c34f |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fbbc49da8c8190902bbb05d2477cab |
completed | May 6, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69fbb13f34b08190bbbb220ac1e6e666 |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:05 p.m.