Triple
T1785087
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fleming valve |
E39372
|
entity |
| Predicate | nonConductingDirection |
P32374
|
FINISHED |
| Object | reverse bias |
—
|
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: reverse bias | Statement: [Fleming valve, nonConductingDirection, reverse bias]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nonConductingDirection Context triple: [Fleming valve, nonConductingDirection, reverse bias]
-
A.
containsDirectionOf
Indicates that one entity includes or encompasses the directional orientation or path associated with another entity.
-
B.
circuitDirection
Indicates the orientation or flow direction of a circuit or circuit path relative to its components or layout.
-
C.
nonElectrifiedSection
Indicates that a segment of a transportation or track network lacks electrical infrastructure for powered operation.
-
D.
primaryDirection
Indicates the main or dominant directional orientation associated with an entity or relation.
-
E.
directionalConfiguration
Indicates a specific spatial or directional arrangement that one entity has relative to another.
- 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_69a88630519c8190a17addd83c4a3ef4 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab75457e54819096b8c6ae8c65550c |
completed | March 7, 2026, 12:45 a.m. |
| PD | Predicate disambiguation | batch_69aa61d165688190924962a98e07ff69 |
completed | March 6, 2026, 5:10 a.m. |
| PDg | Predicate description generation | batch_69ab75444d28819091c393e62fc97f82 |
completed | March 7, 2026, 12:45 a.m. |
Created at: March 4, 2026, 7:31 p.m.